chore: apply markdownlint rules

Author: pichlermarc

.github/ISSUE_TEMPLATE/bug_report.md

@@ -4,7 +4,7 @@ about: Create a report to help us improve
 labels: bug
 ---
 
-<!-- 
+<!--
 Please answer these questions before submitting a bug report.
 -->
 
@@ -15,7 +15,7 @@ Please answer these questions before submitting a bug report.
 
 
 ### What did you do?
-<!-- 
+<!--
 If possible, provide a recipe for reproducing the error.
 -->
 
@@ -27,8 +27,8 @@ If possible, provide a recipe for reproducing the error.
 
 
 ### Additional context
-<!-- 
+<!--
 Add any other context about the problem here.
 -->
 
-<sub>**Tip**: [React](https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/) with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it. Learn more [here](https://opentelemetry.io/community/end-user/issue-participation/).</sub>
+<sub>**Tip**: [React](https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/) with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it. [Learn more here](https://opentelemetry.io/community/end-user/issue-participation/).</sub>

.github/ISSUE_TEMPLATE/discussion.md

@@ -11,5 +11,5 @@ labels: discussion
 - [ ] This only affects the JavaScript OpenTelemetry library
 - [ ] This may affect other libraries, but I would like to get opinions here first
 
-<sub>**Tip**: [React](https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/) with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it. Learn more [here](https://opentelemetry.io/community/end-user/issue-participation/).</sub>
+<sub>**Tip**: [React](https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/) with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it. [Learn more here](https://opentelemetry.io/community/end-user/issue-participation/).</sub>
 

.github/ISSUE_TEMPLATE/feature_request.md

@@ -15,21 +15,21 @@ A clear and concise description of what the problem is. Ex. I'm always frustrate
 
 
 ### Describe the solution you'd like to see
-<!-- 
+<!--
 A clear and concise description of what you want to happen.
 -->
 
 
 ### Describe alternatives you've considered
-<!-- 
+<!--
 A clear and concise description of any alternative solutions or features you've considered.
 -->
 
 
 ### Additional context
-<!-- 
+<!--
 Add any other context or screenshots about the feature request here.
 -->
 
-<sub>**Tip**: [React](https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/) with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it. Learn more [here](https://opentelemetry.io/community/end-user/issue-participation/).</sub>
+<sub>**Tip**: [React](https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/) with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it. [Learn more here](https://opentelemetry.io/community/end-user/issue-participation/).</sub>
 

.github/ISSUE_TEMPLATE/instrumentation_request.md

@@ -35,4 +35,4 @@ Any code-owners listed MUST fulfill all criteria laid out in the checklist below
 Add any other context or screenshots about the instrumentation request here. Is there a reference you could point for the well-defined lifecycle methods?
 -->
 
-<sub>**Tip**: [React](https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/) with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it. Learn more [here](https://opentelemetry.io/community/end-user/issue-participation/).</sub>
+<sub>**Tip**: [React](https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/) with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it. [Learn more here](https://opentelemetry.io/community/end-user/issue-participation/).</sub>

.github/ISSUE_TEMPLATE/ownership_request.md

@@ -39,4 +39,4 @@ Examples:
 Add any other context that does not fit any of the above sections
 -->
 
-<sub>**Tip**: [React](https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/) with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it. Learn more [here](https://opentelemetry.io/community/end-user/issue-participation/).</sub>
+<sub>**Tip**: [React](https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/) with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it. [Learn more here](https://opentelemetry.io/community/end-user/issue-participation/).</sub>

CONTRIBUTING.md

@@ -61,7 +61,7 @@ for general practices for OpenTelemetry project.
 
 #### Conventional commit
 
-The Conventional Commits specification is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an explicit commit history; which makes it easier to write automated tools on top of. This convention dovetails with SemVer, by describing the features, fixes, and breaking changes made in commit messages. You can see examples [here](https://www.conventionalcommits.org/en/v1.0.0/#examples).
+The Conventional Commits specification is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an explicit commit history; which makes it easier to write automated tools on top of. This convention dovetails with SemVer, by describing the features, fixes, and breaking changes made in commit messages. You can see examples [in the conventional commits specification](https://www.conventionalcommits.org/en/v1.0.0/#examples).
 
 We use [the "pr-title" CI workflow](./.github/workflows/pr-title.yml) to ensure PR titles, and hence the commit message from those PRs, follow the Conventional Commits spec.
 
@@ -352,7 +352,7 @@ Review the guidelines for [Becoming a Component Owner](#becoming-a-component-own
 
 Regardless of where instrumentation is hosted, it needs to be discoverable.
 The [OpenTelemetry registry](https://opentelemetry.io/registry/) exists to ensure that instrumentation is discoverable.
-You can find out how to add instrumentation to the registry [here](https://github.com/open-telemetry/opentelemetry.io#adding-a-project-to-the-opentelemetry-registry).
+You can find out how to add instrumentation to the registry [over at opentelemetry.io](https://github.com/open-telemetry/opentelemetry.io#adding-a-project-to-the-opentelemetry-registry).
 
 ## Contributing Vendor Components
 

packages/auto-instrumentations-node/README.md

@@ -173,7 +173,7 @@ registerInstrumentations({
 - [@opentelemetry/instrumentation-express](https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/packages/instrumentation-express)
 - [@opentelemetry/instrumentation-fastify](https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/packages/instrumentation-fastify) (deprecated, default disabled)
   - This component is **deprecated** in favor of the official instrumentation package [`@fastify/otel`](https://www.npmjs.com/package/@fastify/otel), maintained by the Fastify authors.
-    - Please see [here](https://github.com/fastify/otel?tab=readme-ov-file#usage) for instructions on how to use `@fastify/otel`.
+    - Please see [the offical plugin's README.md](https://github.com/fastify/otel?tab=readme-ov-file#usage) for instructions on how to use `@fastify/otel`.
   - This component will be removed on June 30, 2025
 - [@opentelemetry/instrumentation-fs](https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/packages/instrumentation-fs) (default disabled)
 - [@opentelemetry/instrumentation-generic-pool](https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/packages/instrumentation-generic-pool)

packages/host-metrics/README.md

@@ -42,8 +42,8 @@ hostMetrics.start();
 
 ## Configuration
 
-| Option         | Type       | Description |
-| -------------- | ---------- | ----------- |
+| Option         | Type       | Description                                                                                                                                                                                                                                                                                                                                                                                  |
+|----------------|------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | `metricGroups` | `string[]` | Optionally specify zero or more groups of metrics to collect. This package can collect many metrics. They are grouped by metric name prefix (see the "Semantic Conventions" section below). If this option is specified, only metrics from the named groups will be collected. For example, `metricGroups: ['process.cpu', 'process.memory']` will limit collection to just those 3 metrics. |
 
 ## Semantic Conventions
@@ -54,30 +54,30 @@ Ref: [opentelemetry-js/issues/4235](https://github.com/open-telemetry/openteleme
 
 Metrics collected:
 
-| Metric                        | Short Description                                         |
-| ----------------------------- | --------------------------------------------------------- |
-| **Group `system.cpu`**        | |
-|   `system.cpu.time`           | Seconds each logical CPU spent on each mode               |
-|   `system.cpu.utilization`    | CPU usage time (0-1)                                      |
-| **Group `system.memory`**     | |
-|   `system.memory.usage`       | Reports memory in use by state                            |
-|   `system.memory.utilization` | Memory usage (0-1)                                        |
-| **Group `system.network`**    | |
-|   `system.network.dropped`    | Count of packets that are dropped                         |
-|   `system.network.errors`     | Count of network errors detected                          |
-|   `system.network.io`         | Network flow direction                                    |
-| **Group `process.cpu`**       | |
-|   `process.cpu.time`          | Total CPU seconds                                         |
-|   `process.cpu.utilization`   | Difference in process.cpu.time since the last measurement |
-| **Group `process.memory`**    | |
-|   `process.memory.usage`      | The amount of physical memory in use                      |
+| Metric                      | Short Description                                         |
+|-----------------------------|-----------------------------------------------------------|
+| **Group `system.cpu`**      |                                                           |
+| `system.cpu.time`           | Seconds each logical CPU spent on each mode               |
+| `system.cpu.utilization`    | CPU usage time (0-1)                                      |
+| **Group `system.memory`**   |                                                           |
+| `system.memory.usage`       | Reports memory in use by state                            |
+| `system.memory.utilization` | Memory usage (0-1)                                        |
+| **Group `system.network`**  |                                                           |
+| `system.network.dropped`    | Count of packets that are dropped                         |
+| `system.network.errors`     | Count of network errors detected                          |
+| `system.network.io`         | Network flow direction                                    |
+| **Group `process.cpu`**     |                                                           |
+| `process.cpu.time`          | Total CPU seconds                                         |
+| `process.cpu.utilization`   | Difference in process.cpu.time since the last measurement |
+| **Group `process.memory`**  |                                                           |
+| `process.memory.usage`      | The amount of physical memory in use                      |
 
 Note: the "Group" names are groupings used by the `metricGroups` configuration option.
 
 Attributes collected:
 
 | Metric                      | Short Description                  |
-| --------------------------- | ---------------------------------- |
+|-----------------------------|------------------------------------|
 | `system.cpu.logical_number` | The logical CPU number             |
 | `system.cpu.state`          | The state of the CPU               |
 | `system.memory.state`       | The memory state                   |

packages/instrumentation-aws-lambda/README.md

@@ -50,12 +50,12 @@ In your Lambda function configuration, add or update the `NODE_OPTIONS` environm
 
 ## AWS Lambda Instrumentation Options
 
-| Options | Type  | Description |
-| --- | --- | --- |
-| `requestHook` | `RequestHook` (function) | Hook for adding custom attributes before lambda starts handling the request. Receives params: `span, { event, context }` |
-| `responseHook` | `ResponseHook` (function) | Hook for adding custom attributes before lambda returns the response. Receives params: `span, { err?, res? }` |
-| `eventContextExtractor` | `EventContextExtractor` (function) | Function for providing custom context extractor in order to support different event types that are handled by AWS Lambda (e.g., SQS, CloudWatch, Kinesis, API Gateway). |
-| `lambdaHandler` | `string` | By default, this instrumentation automatically determines the Lambda handler function to instrument. This option is used to override that behavior by explicitly specifying the Lambda handler to instrument. See [Specifying the Lambda Handler](#specifying-the-lambda-handler) for additional information. |
+| Options                 | Type                               | Description                                                                                                                                                                                                                                                                                                   |
+|-------------------------|------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `requestHook`           | `RequestHook` (function)           | Hook for adding custom attributes before lambda starts handling the request. Receives params: `span, { event, context }`                                                                                                                                                                                      |
+| `responseHook`          | `ResponseHook` (function)          | Hook for adding custom attributes before lambda returns the response. Receives params: `span, { err?, res? }`                                                                                                                                                                                                 |
+| `eventContextExtractor` | `EventContextExtractor` (function) | Function for providing custom context extractor in order to support different event types that are handled by AWS Lambda (e.g., SQS, CloudWatch, Kinesis, API Gateway).                                                                                                                                       |
+| `lambdaHandler`         | `string`                           | By default, this instrumentation automatically determines the Lambda handler function to instrument. This option is used to override that behavior by explicitly specifying the Lambda handler to instrument. See [Specifying the Lambda Handler](#specifying-the-lambda-handler) for additional information. |
 
 ### Hooks Usage Example
 
@@ -148,7 +148,7 @@ This package uses `@opentelemetry/semantic-conventions` version `1.22+`, which i
 Attributes collected:
 
 | Attribute          | Short Description                                                         |
-| ------------------ | ------------------------------------------------------------------------- |
+|--------------------|---------------------------------------------------------------------------|
 | `cloud.account.id` | The cloud account ID the resource is assigned to.                         |
 | `faas.execution`   | The execution ID of the current function execution.                       |
 | `faas.id`          | The unique ID of the single function that this runtime instance executes. |