fix: Markdownlint issues

Author: rnishtala-sumo

README.md

@@ -201,11 +201,11 @@ The ⚠️ ~~strikethrough~~ ⚠️ components are deprecated.
 [mongodbatlasreceiver]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/receiver/mongodbatlasreceiver
 [mysqlreceiver]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/receiver/mysqlreceiver
 [nginxreceiver]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/receiver/nginxreceiver
-[nopreceiver]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.1/receiver/nopreceiver
+[nopreceiver]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.0/receiver/nopreceiver
 [nsxtreceiver]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/receiver/nsxtreceiver
 [opencensusreceiver]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/receiver/opencensusreceiver
 [oracledbreceiver]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/receiver/oracledbreceiver
-[otlpreceiver]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.1/receiver/otlpreceiver
+[otlpreceiver]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.0/receiver/otlpreceiver
 [otlpjsonfilereceiver]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/receiver/otlpjsonfilereceiver
 [podmanreceiver]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/receiver/podmanreceiver
 [postgresqlreceiver]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/receiver/postgresqlreceiver
@@ -242,7 +242,7 @@ The ⚠️ ~~strikethrough~~ ⚠️ components are deprecated.
 [zipkinreceiver]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/receiver/zipkinreceiver
 [zookeeperreceiver]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/receiver/zookeeperreceiver
 [attributesprocessor]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/processor/attributesprocessor
-[batchprocessor]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.1/processor/batchprocessor
+[batchprocessor]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.0/processor/batchprocessor
 [cascadingfilterprocessor]: ./pkg/processor/cascadingfilterprocessor
 [cumulativetodeltaprocessor]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/processor/cumulativetodeltaprocessor
 [deltatorateprocessor]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/processor/deltatorateprocessor
@@ -254,7 +254,7 @@ The ⚠️ ~~strikethrough~~ ⚠️ components are deprecated.
 [k8sattributesprocessor]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/processor/k8sattributesprocessor
 [logdedupprocessor]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/processor/logdedupprocessor
 [logstransformprocessor]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/processor/logstransformprocessor
-[memorylimiterprocessor]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.1/processor/memorylimiterprocessor
+[memorylimiterprocessor]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.0/processor/memorylimiterprocessor
 [metricfrequencyprocessor]: ./pkg/processor/metricfrequencyprocessor
 [metricstransformprocessor]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/processor/metricstransformprocessor
 [probabilisticsamplerprocessor]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/processor/probabilisticsamplerprocessor
@@ -274,13 +274,13 @@ The ⚠️ ~~strikethrough~~ ⚠️ components are deprecated.
 [awss3exporter]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/exporter/awss3exporter
 [awskinesisexporter]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/exporter/awskinesisexporter
 [carbonexporter]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/exporter/carbonexporter
-[debugexporter]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.1/exporter/debugexporter
+[debugexporter]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.0/exporter/debugexporter
 [fileexporter]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/exporter/fileexporter
 [kafkaexporter]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/exporter/kafkaexporter
 [loadbalancingexporter]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/exporter/loadbalancingexporter
-[nopexporter]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.1/exporter/nopexporter
-[otlpexporter]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.1/exporter/otlpexporter
-[otlphttpexporter]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.1/exporter/otlphttpexporter
+[nopexporter]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.0/exporter/nopexporter
+[otlpexporter]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.0/exporter/otlpexporter
+[otlphttpexporter]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.0/exporter/otlphttpexporter
 [prometheusexporter]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/exporter/prometheusexporter
 [sumologicexporter]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/exporter/sumologicexporter
 [syslogexporter]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/exporter/syslogexporter
@@ -304,8 +304,8 @@ The ⚠️ ~~strikethrough~~ ⚠️ components are deprecated.
 [pprofextension]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/extension/pprofextension
 [sigv4authextension]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/extension/sigv4authextension
 [sumologicextension]: ./pkg/extension/sumologicextension
-[zpagesextension]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.1/extension/zpagesextension
-[forwardconnector]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.1/connector/forwardconnector
+[zpagesextension]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.0/extension/zpagesextension
+[forwardconnector]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.0/connector/forwardconnector
 [countconnector]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/connector/countconnector
 [failoverconnector]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/connector/failoverconnector
 [exceptionsconnector]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/connector/exceptionsconnector

docs/configuration.md

@@ -225,7 +225,7 @@ service:
       exporters: [sumologic]
 ```
 
-[otlpreceiver_readme]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.1/receiver/otlpreceiver
+[otlpreceiver_readme]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.0/receiver/otlpreceiver
 
 ### Putting it all together
 
@@ -533,7 +533,7 @@ Example configuration with example log can be found in [/examples/otelcolconfigs
 
 [json_parser]: https://github.com/open-telemetry/opentelemetry-log-collection/blob/main/docs/operators/json_parser.md
 [filelogreceiver_readme]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/v0.124.1/receiver/filelogreceiver
-[debugexporter_docs]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.1/exporter/debugexporter
+[debugexporter_docs]: https://github.com/open-telemetry/opentelemetry-collector/tree/v0.124.0/exporter/debugexporter
 
 ## Setting source category
 

docs/fips.md

@@ -73,7 +73,7 @@ following: <https://go.googlesource.com/go/+/dev.boringcrypto/misc/boring/>
 Depending on configuration, Otelcol can act as a TLS client, server, or both. More specifically,
 some receivers can accept data via a TLS-wrapped protocol like HTTP or GRPC. Similarly, some
 exporters can send data using such a protocol. The configuration is standardized and can be
-found [here](https://github.com/open-telemetry/opentelemetry-collector/blob/main/config/configtls/README.md).
+found in the [readme](https://github.com/open-telemetry/opentelemetry-collector/blob/main/config/configtls/README.md).
 
 For the purpose of examining the TLS handshake in both of these situations, we'll use the following minimal
 configuration:
@@ -175,7 +175,7 @@ client point: uncompressed (0)
 
 ## Setting minimum TLS version
 
-While [FIPS 140][fips] doesn't, strictly speaking, mandate a specific TLS version, it is nonetheless a good practice to use a recent version. Otelcol allows TLS to be configured for each component individually, in a standardized manner. You can find the details [here](https://github.com/open-telemetry/opentelemetry-collector/blob/main/config/configtls/README.md).
+While [FIPS 140][fips] doesn't, strictly speaking, mandate a specific TLS version, it is nonetheless a good practice to use a recent version. Otelcol allows TLS to be configured for each component individually, in a standardized manner. You can find the details in the [readme](https://github.com/open-telemetry/opentelemetry-collector/blob/main/config/configtls/README.md).
 
 By default, the minimum TLS version for otel components is `1.2`. This is a good default that is compliant with the standard. At the moment, there is some uncertainty as to
 whether BoringCrypto is FIPS-compliant when using TLS `1.3`, so we recommend staying with the default.

docs/migration.md

@@ -1514,7 +1514,7 @@ The table below shows how some metrics commonly used by the Installed Collector
 |                                   |                                                 |                     |
 | current                           | _not available_                                 |                     |
 
-Full list of metrics available in this receiver can be found [here][dockerstatsmetrics].
+Full list of metrics available in this receiver can be found in the [documentation][dockerstatsmetrics].
 
 Unfortunately, Sumo Logic apps don't work with these metric names yet. To convieniently translate them, use [Sumo Logic Schema Processor][sumologicschemaprocessor]:
 

docs/testing.md

@@ -5,7 +5,7 @@
 We currently have some legacy E2E tests ported from [our OT fork][ot_fork],
 which serve as a means of verifying feature parity for tracing as we migrate it
 to this distribution. The tests are run by CircleCI on demand for `main` and
-release branches, and are defined [here][tracing_tests].
+release branches, and are defined in the [tests][tracing_tests].
 
 In order to run the tests, go to the [CircleCI page][circleci], choose the branch
 you want, and manually approve the workflow to run. Note that you need commiter

docs/upgrading.md

@@ -645,7 +645,7 @@ To disable the new features, disable the feature gates in otelcol's arguments:
 otelcol-sumo --config=file:config.yaml --feature-gates=-receiver.apache.emitServerNameAsResourceAttribute,-receiver.apache.emitPortAsResourceAttribute
 ```
 
-More information about the feature gates can be found [here][apache-feature-gates].
+More information about the feature gates can be found in the [documentation][apache-feature-gates].
 The target release for the removal of feature gates is `v0.68`.
 
 ### `elasticsearch` receiver: turn on more datapoints
@@ -661,7 +661,7 @@ To disable the new features, disable the feature gates in otelcol's arguments:
 otelcol-sumo --config=file:config.yaml --feature-gates=-receiver.elasticsearch.emitClusterHealthDetailedShardMetrics,-receiver.elasticsearch.emitAllIndexOperationMetrics
 ```
 
-More information about the feature gates can be found [here][elasticsearch-feature-gates].
+More information about the feature gates can be found in the [documentation][elasticsearch-feature-gates].
 The target release for the removal of feature gates is `v0.71`.
 
 [#5784]: https://github.com/open-telemetry/opentelemetry-collector/pull/5784
@@ -856,8 +856,8 @@ processors:
 ```
 
 Starting with `v0.51.0-sumo-0`, the `clusterName` option is removed.
-This is a result of an upstream change that removes the `k8s.cluster.name` metadata ([link](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/9885)),
-which in turn is a result of Kubernetes libraries removing support for this deprecated and non-functional field ([link](https://github.com/kubernetes/apimachinery/commit/430b920312ca0fa10eca95967764ff08f34083a3)).
+This is a result of an upstream change that removes the `k8s.cluster.name` metadata ([PR](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/9885)),
+which in turn is a result of Kubernetes libraries removing support for this deprecated and non-functional field ([commit](https://github.com/kubernetes/apimachinery/commit/430b920312ca0fa10eca95967764ff08f34083a3)).
 
 #### How to upgrade
 

pkg/extension/sumologicextension/README.md

@@ -16,7 +16,7 @@ It manages:
   for later use)
 - heartbeats
 
-[sumologicexporter]: ../../exporter/sumologicexporter/
+[sumologicexporter]: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/sumologicexporter/README.md
 [sumologic]: https://www.sumologic.com/
 [sumologic_extension_docs]: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/extension/sumologicextension/README.md
 [contrib_repo]: https://github.com/open-telemetry/opentelemetry-collector-contrib/
@@ -34,7 +34,7 @@ and can be used as an authenticator for the
 
 - `installation_token`: (required) collector installation token for the Sumo Logic service, see
   [help][credentials_help] for more details
-- `collector_name`: name that will be used for registration; by default the hostname is used. In the event of a conflict, a timestamp will be appended to the name. See [here][clobber] for more information.
+- `collector_name`: name that will be used for registration; by default the hostname is used. In the event of a conflict, a timestamp will be appended to the name. See [documentation][clobber] for more information.
 - `collector_description`: collector description that will be used for registration
 - `collector_category`: collector category that will be used for registration
 - `collector_fields`: a map of key value pairs that will be used as collector
@@ -52,7 +52,7 @@ and can be used as an authenticator for the
 - `collector_credentials_directory`: directory where state files with registration
   info will be stored after successful collector registration
   (default: `$HOME/.sumologic-otel-collector`)
-- `clobber`: defines whether to delete any existing collector with the same name. See [here][clobber] for more information.
+- `clobber`: defines whether to delete any existing collector with the same name. See [documentation][clobber] for more information.
 - `force_registration`: defines whether to force registration every time the
   collector starts.
   This will cause the collector to not look at the locally stored credentials