chore: convert all shortcut ref links to collapsed form, and fix links (#9252)

Author: chalin

.markdownlint.yaml

@@ -43,9 +43,9 @@ table-column-style: false # Causes problems in ja and zh pages
 no-shortcut-ref-link:
   # Skip:
   # - OTel spec informal footnotes like [1], [2]
-  # - Markdown footnote references like [^1], [^note]
+  # - SemConf number ranges like [0..1], [0..n-1], [0.0, 1.0]
   # - Ellipsis like [...]
-  ignore_pattern: '^\d+(\.\.\d+)?$|^\.\.\.$' # skip [1], [2], [0..1], etc.
+  ignore_pattern: '^([-+,n\d\.\s]+)$|^\.\.\.$'
 
 # -----------------------------------------------------------------------------
 # Link-validation rules (from scripts/_md-rules/link-rules.mjs)

content/bn/docs/concepts/glossary.md

@@ -19,8 +19,7 @@ drifted_from_default: true
 
 একটি নির্দিষ্ট সময়ের ব্যবধানে, প্রোগ্রাম এক্সিকিউশনের সময় ঘটে যাওয়া
 পরিমাপগুলোর সম্পর্কে সুনির্দিষ্ট বা অনুমানভিত্তিক পরিসংখ্যানে একাধিক
-পরিমাপকে একত্রিত করার প্রক্রিয়া। [Metric](#metric) [Data source]
-(#data-source) দ্বারা ব্যবহৃত।
+পরিমাপকে একত্রিত করার প্রক্রিয়া। [Metric](#metric) [Data source](#data-source) দ্বারা ব্যবহৃত।
 
 ### API {#api}
 
@@ -66,11 +65,11 @@ Application Performance Monitoring হল সফটওয়্যার অ্
 
 ### কালেক্টর (Collector) {#collector}
 
-[OpenTelemetry Collector], বা সংক্ষেপে Collector, হল টেলিমেট্রি ডেটা গ্রহণ, প্রক্রিয়াকরণ এবং
+[OpenTelemetry Collector][], বা সংক্ষেপে Collector, হল টেলিমেট্রি ডেটা গ্রহণ, প্রক্রিয়াকরণ এবং
 রপ্তানির একটি ভেন্ডর-এগ্নস্টিক (vendor-agnostic) বাস্তবায়ন। এটি একটি একক বাইনারি যা agent বা
 gateway হিসেবে ডিপ্লয় (deploy) করা যায়।
 
-> **বানান**: [OpenTelemetry Collector] উল্লেখ করার সময়, সর্বদা Collector
+> **বানান**: [OpenTelemetry Collector][] উল্লেখ করার সময়, সর্বদা Collector
 > বড় অক্ষরে লিখুন। আপনি যদি Collector-কে বিশেষণ হিসেবে ব্যবহার করেন তাহলে শুধু "Collector"
 > ব্যবহার করুন — উদাহরণস্বরূপ, "Collector configuration"।
 
@@ -265,7 +264,7 @@ OpenTelemetry-এর পূর্বসূরি। বিস্তারিত
 
 ### OTEP {#otep}
 
-[OpenTelemetry Enhancement Proposal]-এর একটি সংক্ষিপ্ত রূপ।
+[OpenTelemetry Enhancement Proposal][]-এর একটি সংক্ষিপ্ত রূপ।
 
 > **বানান**: বহুবচন হিসেবে "OTEPs" লিখুন। বর্ণনায় `OTep` বা `otep`
 > লিখবেন না।

content/bn/docs/what-is-opentelemetry.md

@@ -92,7 +92,7 @@ OpenTelemetry হলো [Cloud Native Computing Foundation][] (CNCF)-এর এ
 
 - [শুরু করুন](../getting-started/) —  OpenTelemetry ব্যবহার শুরু করুন সহজেই।
 - [OpenTelemetry এর কনসেপ্টগুলো](../concepts/)  সম্পর্কে জানুন।
-- [ভিডিও দেখুন][watch videos] — [OTel for beginners] ও অন্যান্য [প্লেলিস্ট][playlists] থেকে।
+- [ভিডিও দেখুন][watch videos] — [OTel for beginners][] ও অন্যান্য [প্লেলিস্ট][playlists] থেকে।
 - সাইন আপ করুন [ট্রেনিং](/training) এর জন্য এবং পেয়ে যান [Getting started with OpenTelemetry](/training/#courses) কোর্সটি একদম বিনামূ��্যে।
 
 [Cloud Native Computing Foundation]: https://www.cncf.io

content/en/blog/2023/contributing-to-otel/index.md

@@ -25,7 +25,7 @@ projects? I don't know about you, but for me, up until last year, the prospect
 of contributing to open source was just plain _scary_!! I mean, when you open up
 a
 [pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests)
-(PR), _[you are putting yourself out there]_, to be judged by those little
+(PR), _[you are putting yourself out there][]_, to be judged by those little
 GitHub avatars that make up the approvers list for the repository you're
 contributing to. YIKES!
 

content/en/blog/2023/logs-collection/index.md

@@ -420,7 +420,7 @@ extend Yoda's code to do the following:
    [transform or attributes processors](/docs/collector/transforming-telemetry/).
 1. Add [tracing](/docs/concepts/signals/traces/) support by emitting spans,
    where it makes sense.
-1. Add an Observability backend such as OpenSearch (along with [Data Prepper])
+1. Add an Observability backend such as OpenSearch (along with [Data Prepper][])
    to the setup, allowing to ingest spans and logs in OTLP format.
 1. Once you have traces and logs ingested in a backend, try to correlate these
    two telemetry signal types in the backend along with a frontend such as

content/en/blog/2024/fuzzing-audit-results.md

@@ -9,7 +9,7 @@ cSpell:ignore: containerd Korczynski
 ---
 
 OpenTelemetry is happy to announce the completion of the Collector's fuzzing
-audit [sponsored by the CNCF] and carried out by
+audit [sponsored by the CNCF][] and carried out by
 [Ada Logics](https://adalogics.com/). The audit marks a significant step in the
 OpenTelemetry project, ensuring the security and reliability of the Collector
 for its users.

content/en/blog/2024/kubecon-eu.md

@@ -10,8 +10,8 @@ cSpell:ignore: Aiven Alexandre Anusha Arbiv Beemer Benedikt Blanco Bongartz Chek
 ---
 
 The OpenTelemetry project maintainers, members of the governance committee, and
-technical committee are thrilled to be at [KubeCon + CloudNativeCon Europe] and
-at the co-located
+technical committee are thrilled to be at [KubeCon + CloudNativeCon Europe][]
+and at the co-located
 [Observability Day](https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/co-located-events/observability-day/)
 in Paris from March 19 - 22, 2024.
 
@@ -46,9 +46,9 @@ it again right before KubeCon!
 
 ## Observability Day
 
-_[Observability Day] fosters collaboration, discussion, and knowledge sharing of
-cloud native observability projects_. This event will be held on March 19, 2024
-from 9:00 - 17:35. There will be several sessions on OpenTelemetry as well:
+_[Observability Day][] fosters collaboration, discussion, and knowledge sharing
+of cloud native observability projects_. This event will be held on March 19,
+2024 from 9:00 - 17:35. There will be several sessions on OpenTelemetry as well:
 
 - **[Welcome + Project Updates](https://sched.co/1YGT9)**<br> by Eduardo Silva,
   FluentBit & Austin Parker, honeycomb.io<br> Tuesday, March 19th • 09:00 -
@@ -90,8 +90,9 @@ from 9:00 - 17:35. There will be several sessions on OpenTelemetry as well:
 > [!IMPORTANT] Important access note
 >
 > You need an _in-person all-access_ pass for on-site access to **Observability
-> Day**. For details, see [KubeCon registration]. If you have a virtual ticket,
-> you will be able to follow **Observability Day** through a live stream.
+> Day**. For details, see [KubeCon registration][]. If you have a virtual
+> ticket, you will be able to follow **Observability Day** through a live
+> stream.
 
 [kubecon registration]:
   https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/register/

content/en/blog/2024/kubecon-na.md

@@ -8,7 +8,7 @@ cSpell:ignore: Arnell Ashok Chandrasekar Clario Contribfest Ekansh Grabner Haeus
 ---
 
 The OpenTelemetry project maintainers, members of the governance committee, and
-technical committee are thrilled to be at [KubeCon NA] in Salt Lake City from
+technical committee are thrilled to be at [KubeCon NA][] in Salt Lake City from
 November 12 - 15, 2024.
 
 Read on to learn about all the things related OpenTelemetry during KubeCon.
@@ -78,16 +78,17 @@ first steps: documentation, Collector, Java, JS, Ruby, Python, .NET, and more.
 
 ## Observability Day
 
-_[Observability Day] fosters collaboration, discussion, and knowledge sharing of
-cloud native observability projects_. This event will be held on November 12,
+_[Observability Day][] fosters collaboration, discussion, and knowledge sharing
+of cloud native observability projects_. This event will be held on November 12,
 2024 from 9am to 6pm.
 [Check the full schedule](https://colocatedeventsna2024.sched.com/overview/type/Observability+Day)
 to find your favorite talks about Observability and OpenTelemetry.
 
 > <i class="far fa-exclamation-triangle"></i> **IMPORTANT access note**: You
 > need an _in-person all-access_ pass for on-site access to **Observability
-> Day**. For details, see [KubeCon registration]. If you have a virtual ticket,
-> you will be able to follow **Observability Day** through a live stream.
+> Day**. For details, see [KubeCon registration][]. If you have a virtual
+> ticket, you will be able to follow **Observability Day** through a live
+> stream.
 
 ## OpenTelemetry Observatory
 

content/en/blog/2024/otel-docs-survey/index.md

@@ -77,7 +77,7 @@ results.
 We asked respondents to describe in their own words what they'd like to see
 added to the [opentelemetry.io][] documentation. We loosely grouped their
 responses into six categories. Some answers fell in more than one category. For
-full responses, see [Docs Usability Survey Responses].
+full responses, see [Docs Usability Survey Responses][].
 
 [Docs Usability Survey Responses]:
   https://docs.google.com/spreadsheets/d/1kpJQYiEGtpZorICbl-QfYL3mKfeoRLiUywvKcV8fcNA
@@ -177,7 +177,7 @@ people that needs the most work is the JavaScript documentation.
 
 ## Learn more
 
-For detailed survey results, see [Docs Usability Survey Responses].
+For detailed survey results, see [Docs Usability Survey Responses][].
 
 ## Your feedback is essential
 

content/en/blog/2024/otel-generative-ai/index.md

@@ -77,7 +77,7 @@ behaviors may arise.
 
 > [!NOTE]
 >
-> Note that we decided to use [events emitted] with the
+> Note that we decided to use [events emitted][] with the
 > [Logs API](/docs/specs/otel/logs/api/) specification in the Semantic
 > Conventions for Generative AI. Events allows for us to define specific
 > [semantic conventions](/docs/specs/semconv/general/events/) for the user