[chore] Accessible links 4

content/en/blog/2022/dotnet-instrumentation-first-beta.md

@@ -57,8 +57,7 @@ Please, give us your **feedback** (using your preferred method):
 
 - [Submit a GitHub issue](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/issues/new).
 - Write to us on [Slack](https://cloud-native.slack.com/archives/C01NR1YLSE7).
-  If you are new, you can create a CNCF Slack account
-  [here](https://slack.cncf.io/).
+  If you are new, you can [create a CNCF Slack account](https://slack.cncf.io/).
 
 [^devopsnote]:
     The

content/en/blog/2022/dotnet-instrumentation-metrics.md

@@ -30,5 +30,4 @@ Please, give us your feedback (using your preferred method):
 
 - [Submit a GitHub issue](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/issues/new).
 - Write to us on [Slack](https://cloud-native.slack.com/archives/C01NR1YLSE7).
-  If you are new, you can create a CNCF Slack account
-  [here](https://slack.cncf.io/).
+  If you are new, you can [create a CNCF Slack account](https://slack.cncf.io/).

content/en/blog/2023/k8s-runtime-observability/index.md

@@ -29,9 +29,9 @@ Here is a brief synopsis of the recent activity in the Kubernetes ecosystem:
   ([KEP 2831 Kubelet Tracing](https://github.com/kubernetes/enhancements/tree/master/keps/sig-instrumentation/2831-kubelet-tracing)).
 - [etcd](https://github.com/etcd-io/etcd) (Kubernetes uses it as an internal
   datastore) started to discuss tracing in November 2020
-  ([here](https://github.com/etcd-io/etcd/issues/12460)) and had a
-  [first version merged](https://github.com/etcd-io/etcd/pull/12919) in
-  May 2021.
+  ([Add Distributed Tracing using OpenTelemetry](https://github.com/etcd-io/etcd/issues/12460))
+  and had a [first version merged](https://github.com/etcd-io/etcd/pull/12919)
+  in May 2021.
 - [containerd](https://github.com/containerd/containerd) and
   [CRI-O](https://github.com/cri-o/cri-o), two Container Runtime Interfaces for
   Kubernetes, started to implement tracing in 2021

content/en/blog/2023/otel-dotnet-auto-instrumentation.md

@@ -29,5 +29,4 @@ Feedback is welcome:
 
 - [Submit a GitHub issue](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/issues/new).
 - Write to us on [Slack](https://cloud-native.slack.com/archives/C01NR1YLSE7).
-  If you are new, you can create a CNCF Slack account
-  [here](https://slack.cncf.io/).
+  If you are new, you can [create a CNCF Slack account](https://slack.cncf.io/).

content/en/blog/2023/testing-otel-demo/index.md

@@ -83,9 +83,8 @@ We structured two types of tests based on
 - Integration tests
 - End-to-end tests
 
-The tests are organized into 26 trace-based tests for 10 services, which can be
-found
-[here](https://github.com/open-telemetry/opentelemetry-demo/tree/main/test/tracetesting).
+The tests are organized into
+[26 trace-based tests for 10 services](https://github.com/open-telemetry/opentelemetry-demo/tree/main/test/tracetesting).
 These trace-based tests in the `tracetesting` directory are ported from AVA and
 Cypress and test both the operation outcome and the traces.
 

content/en/blog/2024/java-metric-systems-compared/index.md

@@ -359,8 +359,8 @@ And now a description of the methodology and how to interpret the data:
 
 - The code supporting these benchmarks is available on at
   [github.com/jack-berg/metric-system-benchmarks](https://github.com/jack-berg/metric-system-benchmarks),
-  with raw result data available
-  [here](https://docs.google.com/spreadsheets/d/1I2ACFAgzWaa1H5EQx99-rLTro2FHlS44gsWuQsU8Ssw/edit#gid=191407209).
+  the
+  [raw result data is available as a Google Sheet](https://docs.google.com/spreadsheets/d/1I2ACFAgzWaa1H5EQx99-rLTro2FHlS44gsWuQsU8Ssw/edit#gid=191407209).
 - Benchmarks were run on my local machine, a MacBook Pro w/ M1 Max, 64GB ram,
   running Sonoma 14.3.1.
 - There are three distinct benchmarks to compare key aspects of the system:

content/en/blog/2024/llm-observability.md

@@ -118,8 +118,7 @@ Before we begin, make sure you have the following running in your environment:
 
 ### Setting Up the OpenTelemetry Collector
 
-First, install the OpenTelemetry Collector. You can find how to do this in the
-installation guide [here](/docs/collector/installation/).
+First, [install the OpenTelemetry Collector](/docs/collector/installation/).
 
 ### Configuring the Collector
 
@@ -229,9 +228,8 @@ any tool of your choice to visualize this data:
 
 #### Add the dashboard
 
-To make things easy, you can use the dashboard the OpenLIT team made. Just grab
-the JSON from
-[here](https://docs.openlit.io/latest/connections/prometheus-jaeger#dashboard).
+To make things easy, you can use
+[the OpenLIT's dashboard](https://docs.openlit.io/latest/connections/prometheus-jaeger#dashboard).
 
 This guide showed you how to use OpenTelemetry, Prometheus, Jaeger, and Grafana
 to monitor your LLM Applications.

content/en/blog/2024/prometheus-compatibility-survey/index.md

@@ -52,10 +52,10 @@ with the help of the [OpenTelemetry End User SIG](/community/end-user/).
 Deciding on the default translation approach is one of the last remaining
 blockers for stabilizing the compatibility specification.
 
-The survey received 86 responses (and 5 spam), and contained many helpful pieces
-of feedback. Thank you to everyone that participated! The questions and raw
-results can be found
-[here](https://github.com/open-telemetry/sig-end-user/blob/main/end-user-surveys/otel-prom-interoperability/otel-prom-interoperability-survey.csv).
+The
+[survey received 86 responses (and 5 spam)](https://github.com/open-telemetry/sig-end-user/blob/main/end-user-surveys/otel-prom-interoperability/otel-prom-interoperability-survey.csv),
+and contained many helpful pieces of feedback. Thank you to everyone that
+participated!
 
 ## Overall takeaways
 

content/en/community/_index.md

@@ -15,10 +15,11 @@ OpenTelemetry maintainers? Check out the
 
 ## Special Interest Groups
 
-We organize the community into Special Interest Groups (SIGs) in order to
-improve our workflow and more easily manage a community project.
-[Read more](https://github.com/open-telemetry/community#special-interest-groups)
-from our [community repository](https://github.com/open-telemetry/community).
+We organize the community into
+[Special Interest Groups (SIGs)](https://github.com/open-telemetry/community#special-interest-groups)
+in order to improve our workflow and more easily manage a community project.
+Read more from our
+[community repository](https://github.com/open-telemetry/community).
 
 ## Ecosystem
 

content/en/docs/collector/building/receiver.md

@@ -9,8 +9,8 @@ cSpell:ignore: backendsystem crand debugexporter loggingexporter mapstructure pc
 <!-- markdownlint-disable heading-increment no-duplicate-heading -->
 
 If you are reading this tutorial, you probably already have an idea of the
-OpenTelemetry concepts behind distributed tracing, but if you don't you can
-quickly read through it [here](/docs/concepts/signals/traces/).
+OpenTelemetry concepts behind
+[distributed tracing](/docs/concepts/signals/traces/).
 
 Here is the definition of those concepts according to OpenTelemetry:
 
@@ -198,8 +198,8 @@ go mod init github.com/open-telemetry/opentelemetry-tutorials/trace-receiver/tai
 >
 > 1. The module path above is a mock path, which can be your desired private or
 >    public path.
-> 2. The initial code is hosted
->    [here](https://github.com/rquedas/otel4devs/tree/main/collector/receiver/trace-receiver).
+> 2. See the
+>    [initial trace-receiver code](https://github.com/rquedas/otel4devs/tree/main/collector/receiver/trace-receiver).
 
 It's recommended to enable Go
 [Workspaces](https://go.dev/doc/tutorial/workspaces) since we're going to manage