[chore] Accessible links 3

content/en/docs/kubernetes/operator/_index.md

@@ -71,5 +71,5 @@ EOF
 
 For more configuration options and for setting up the injection of
 auto-instrumentation of the workloads using OpenTelemetry instrumentation
-libraries, continue reading
-[here](https://github.com/open-telemetry/opentelemetry-operator/blob/main/README.md).
+libraries, see
+[OpenTelemetry Operator for Kubernetes](https://github.com/open-telemetry/opentelemetry-operator/blob/main/README.md).

content/en/docs/languages/erlang/instrumentation.md

@@ -200,9 +200,8 @@ _ = Task.await(task)
 ### Linking the New Span
 
 A [Span](/docs/concepts/signals/traces/#spans) can be created with zero or more
-Span Links that causally link it to another Span. A
-[Link](/docs/concepts/signals/traces/#span-links) needs a Span context to be
-created.
+[Span Links](/docs/concepts/signals/traces/#span-links) that causally link it to
+another Span. A Span Link needs a Span context to be created.
 
 {{< tabpane text=true >}} {{% tab Erlang %}}
 

content/en/docs/languages/js/getting-started/nodejs.md

@@ -13,8 +13,8 @@ the console.
 
 {{% alert title="Note" color="info" %}} The logging library for OpenTelemetry
 for Node.js is still under development hence an example for it is not provided
-below. Look [here](/docs/languages/js) for more info about the status of
-OpenTelemetry in JavaScript. {{% /alert %}}
+below. For status details, see
+[Status and Releases](/docs/languages/js/#status-and-releases). {{% /alert %}}
 
 ## Prerequisites
 

content/en/docs/languages/js/resources.md

@@ -249,9 +249,9 @@ DockerCGroupV1Detector found resource. Resource {
 ## Next steps
 
 There are more resource detectors you can add to your configuration, for example
-to get details about your [Cloud] environment or [Deployment][]. You will find a
-list
-[here](https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/detectors/node).
+to get details about your [Cloud] environment or [Deployment]. For more, see the
+complete
+[list of detectors](https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/detectors/node).
 
 [getting started - node.js]: /docs/languages/js/getting-started/nodejs/
 [process and process runtime resources]: /docs/specs/semconv/resource/process/

content/en/docs/languages/net/exporters.md

@@ -289,8 +289,8 @@ var app = builder.Build();
 app.UseOpenTelemetryPrometheusScrapingEndpoint();
 ```
 
-Further details on configuring the Prometheus exporter can be found
-[here](https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry.Exporter.Prometheus.AspNetCore/README.md).
+For more details on configuring the Prometheus exporter, see
+[OpenTelemetry.Exporter.Prometheus.AspNetCore](https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry.Exporter.Prometheus.AspNetCore/README.md).
 
 {{% docs/languages/exporters/zipkin-setup %}}
 

content/en/docs/zero-code/java/spring-boot-starter/other-spring-autoconfig.md

@@ -25,8 +25,8 @@ for the list of supported libraries and features.
 If an exporter is present in the classpath during runtime and a spring bean of
 the exporter is missing from the spring application context, an exporter bean is
 initialized and added to a simple span processor in the active tracer provider.
-Check out the implementation
-[here](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/instrumentation/spring/spring-boot-autoconfigure/src/main/java/io/opentelemetry/instrumentation/spring/autoconfigure/OpenTelemetryAutoConfiguration.java).
+For more details, see the
+[implementation (OpenTelemetryAutoConfiguration.java)](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/instrumentation/spring/spring-boot-autoconfigure/src/main/java/io/opentelemetry/instrumentation/spring/autoconfigure/OpenTelemetryAutoConfiguration.java).
 
 {{< tabpane text=true >}} {{% tab header="Maven (`pom.xml`)" lang=Maven %}}
 

content/en/docs/zero-code/js/configuration.md

@@ -17,8 +17,8 @@ and more.
 
 ## SDK and exporter configuration
 
-SDK and exporter configuration can be set using environment variables. More
-information can be found [here](/docs/languages/sdk-configuration/).
+[SDK and exporter configuration](/docs/languages/sdk-configuration/) can be set
+using environment variables.
 
 ## SDK resource detector configuration
 

content/en/docs/zero-code/net/troubleshooting.md

@@ -2,7 +2,7 @@
 title: Troubleshooting .NET automatic instrumentation issues
 linkTitle: Troubleshooting
 weight: 50
-cSpell:ignore: COREHOST corehost NETFX netfx TRACEFILE
+cSpell:ignore: COREHOST corehost NETFX netfx pjanotti's TRACEFILE
 ---
 
 ## General steps
@@ -167,7 +167,7 @@ If you are having problems in one of the scenarios above run again the
 ensure that the required GAC installations are updated.
 
 For more information about the GAC usage by the automatic instrumentation, see
-[here](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/issues/1906#issuecomment-1376292814).
+[pjanotti's comment](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/issues/1906#issuecomment-1376292814).
 
 See
 [#2269](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/issues/2269)

content/en/docs/zero-code/python/configuration.md

@@ -120,8 +120,9 @@ outputted.
 - `OTEL_PYTHON_LOG_LEVEL`: to set a custom log level (info, error, debug,
   warning)
 - `OTEL_PYTHON_LOGGING_AUTO_INSTRUMENTATION_ENABLED`: to enable
-  auto-instrumentation of logs. Attaches OTLP handler to Python root logger. See
-  example [here](/docs/zero-code/python/logs-example)
+  auto-instrumentation of logs. Attaches OTLP handler to Python root logger. For
+  an example, see
+  [Logs Auto-Instrumentation](/docs/zero-code/python/logs-example/).
 
 Examples:
 

content/en/docs/zero-code/python/logs-example.md

@@ -23,8 +23,8 @@ auto-instrumentation of logs. The example below is based on the logs example in
 > There is a logs bridge API; however, it is different from the Traces and
 > Metrics API, because it's not used by application developers to create logs.
 > Instead, they would use this bridge API to setup log appenders in the standard
-> language-specific logging libraries. More information can be found
-> [here](/docs/specs/otel/logs/api/).
+> language-specific logging libraries. For more information, see
+> [Logs API](/docs/specs/otel/logs/api/).
 
 Start by creating the examples directory and the example Python file:
 
@@ -51,9 +51,9 @@ with tracer.start_as_current_span("foo"):
     logging.getLogger().error("This is a log message")
 ```
 
-Grab a copy of the OTel Collector configuration from
-[here](https://github.com/open-telemetry/opentelemetry-python/blob/main/docs/examples/logs/otel-collector-config.yaml),
-and save it to `python-logs-example/otel-collector-config.yaml`
+Open and copy the
+[otel-collector-config.yaml](https://github.com/open-telemetry/opentelemetry-python/blob/main/docs/examples/logs/otel-collector-config.yaml)
+example, and save it to `python-logs-example/otel-collector-config.yaml`
 
 ## Prepare