[chore] move to gfm alerts also supported in hugo (#3112)

thompson-tomo · trask · web-flow · commit 6836ec15d64e · 2025-11-26T04:04:12.000Z
Co-authored-by: Trask Stalnaker &lt;trask.stalnaker@gmail.com&gt;
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -342,7 +342,8 @@ You can perform all checks locally using this command:
 make check
 ```
 
-> Note: `make check` can take a long time as it checks all links.
+> [!Note]
+> `make check` can take a long time as it checks all links.
 > You should use this prior to submitting a PR to ensure validity.
 > However, you can run individual checks directly.
 
@@ -406,7 +407,8 @@ To check for typos, run the following command:
 make misspell
 ```
 
-> **NOTE**: The `misspell` make target will also fetch and build the tool if
+> [!Note]
+> The `misspell` make target will also fetch and build the tool if
 > necessary. You'll need [Go](https://go.dev) to build the spellchecker.
 
 To quickly fix typos, use
diff --git a/docs/db/README.md b/docs/db/README.md
@@ -10,7 +10,7 @@ aliases: [/docs/specs/semconv/database]
 This document defines semantic conventions for database client spans as well as
 database metrics and logs.
 
-> **Warning**
+> [!IMPORTANT]
 >
 > Existing database instrumentations that are using
 > [v1.24.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.24.0/docs/database/database-spans.md)
diff --git a/docs/db/database-metrics.md b/docs/db/database-metrics.md
@@ -27,7 +27,7 @@ aliases: [/docs/specs/semconv/database/database-metrics.md]
 
 <!-- tocstop -->
 
-> **Warning**
+> [!IMPORTANT]
 >
 > Existing database instrumentations that are using
 > [v1.24.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.24.0/docs/database/database-spans.md)
diff --git a/docs/db/database-spans.md b/docs/db/database-spans.md
@@ -20,7 +20,7 @@ aliases: [/docs/specs/semconv/database/database-spans.md]
 
 <!-- tocstop -->
 
-> **Warning**
+> [!IMPORTANT]
 >
 > Existing database instrumentations that are using
 > [v1.24.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.24.0/docs/database/database-spans.md)
diff --git a/docs/feature-flags/feature-flags-events.md b/docs/feature-flags/feature-flags-events.md
@@ -28,7 +28,7 @@ This can be used to determine the impact a feature has on a request, enabling en
 
 Feature flag evaluations SHOULD be recorded as attributes on the [Event](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.51.0/specification/logs/data-model.md#events) passed to the [Logger](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.51.0/specification/logs/api.md#logger) emit operations.
 
-> Note:
+> [!NOTE]
 > Events are in-development and not yet available in some languages. Check the [spec-compliance matrix](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.51.0/spec-compliance-matrix.md#logs) to see the implementation status in the corresponding language.
 
 ## Evaluation event
diff --git a/docs/gen-ai/README.md b/docs/gen-ai/README.md
@@ -6,7 +6,7 @@ linkTitle: Generative AI
 
 **Status**: [Development][DocumentStatus]
 
-> [!Warning]
+> [!IMPORTANT]
 >
 > Existing GenAI instrumentations that are using
 > [v1.36.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.36.0/docs/gen-ai/README.md)
diff --git a/docs/gen-ai/aws-bedrock.md b/docs/gen-ai/aws-bedrock.md
@@ -6,7 +6,7 @@ linkTitle: AWS Bedrock
 
 **Status**: [Development][DocumentStatus]
 
-> [!Warning]
+> [!IMPORTANT]
 >
 > Existing GenAI instrumentations that are using
 > [v1.36.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.36.0/docs/gen-ai/README.md)
diff --git a/docs/gen-ai/azure-ai-inference.md b/docs/gen-ai/azure-ai-inference.md
@@ -15,7 +15,7 @@ linkTitle: Azure AI Inference
 
 <!-- tocstop -->
 
-> [!Warning]
+> [!IMPORTANT]
 >
 > Existing GenAI instrumentations that are using
 > [v1.36.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.36.0/docs/gen-ai/README.md)
diff --git a/docs/gen-ai/gen-ai-agent-spans.md b/docs/gen-ai/gen-ai-agent-spans.md
@@ -15,7 +15,7 @@ linkTitle: Agent spans
 
 <!-- tocstop -->
 
-> [!Warning]
+> [!IMPORTANT]
 >
 > Existing GenAI instrumentations that are using
 > [v1.36.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.36.0/docs/gen-ai/README.md)
diff --git a/docs/gen-ai/gen-ai-events.md b/docs/gen-ai/gen-ai-events.md
@@ -13,7 +13,7 @@ linkTitle: Events
 
 <!-- tocstop -->
 
-> [!Warning]
+> [!IMPORTANT]
 >
 > Existing GenAI instrumentations that are using
 > [v1.36.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.36.0/docs/gen-ai/README.md)
@@ -36,7 +36,7 @@ linkTitle: Events
 
 GenAI instrumentations MAY capture user inputs sent to the model and responses received from it as [events](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.51.0/specification/logs/data-model.md#events).
 
-> Note:
+> [!Note]
 > Events are in-development and not yet available in some languages. Check [spec-compliance matrix](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.51.0/spec-compliance-matrix.md#logs) to see the implementation status in corresponding language.
 
 ## Event: `event.gen_ai.client.inference.operation.details`
diff --git a/docs/gen-ai/gen-ai-metrics.md b/docs/gen-ai/gen-ai-metrics.md
@@ -18,7 +18,7 @@ linkTitle: Metrics
 
 <!-- tocstop -->
 
-> [!Warning]
+> [!IMPORTANT]
 >
 > Existing GenAI instrumentations that are using
 > [v1.36.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.36.0/docs/gen-ai/README.md)
diff --git a/docs/gen-ai/gen-ai-spans.md b/docs/gen-ai/gen-ai-spans.md
@@ -20,7 +20,7 @@ linkTitle: Spans
 
 <!-- tocstop -->
 
-> [!Warning]
+> [!IMPORTANT]
 >
 > Existing GenAI instrumentations that are using
 > [v1.36.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.36.0/docs/gen-ai/README.md)
diff --git a/docs/gen-ai/openai.md b/docs/gen-ai/openai.md
@@ -17,7 +17,7 @@ linkTitle: OpenAI
 
 <!-- tocstop -->
 
-> [!Warning]
+> [!IMPORTANT]
 >
 > Existing GenAI instrumentations that are using
 > [v1.36.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.36.0/docs/gen-ai/README.md)
diff --git a/docs/general/attributes.md b/docs/general/attributes.md
@@ -58,7 +58,7 @@ identify the transport, then setting [`network.transport`](#other-network-attrib
 
 ### Server attributes
 
-> **Warning**
+> [!IMPORTANT]
 > Attributes in this section are in use by the HTTP semantic conventions.
 Once the HTTP semantic conventions are declared stable, changes to the attributes in this section will only be allowed
 if they do not cause breaking changes to HTTP semantic conventions.
@@ -104,7 +104,7 @@ For Unix domain socket, `server.address` attribute represents remote endpoint ad
 
 ### Client attributes
 
-> **Warning**
+> [!IMPORTANT]
 > Attributes in this section are in use by the HTTP semantic conventions.
 Once the HTTP semantic conventions are declared stable, changes to the attributes in this section will only be allowed
 if they do not cause breaking changes to HTTP semantic conventions.
@@ -184,7 +184,7 @@ Destination fields capture details about the receiver of a network exchange/pack
 
 ### Other network attributes
 
-> **Warning**
+> [!IMPORTANT]
 > Attributes in this section are in use by the HTTP semantic conventions.
 Once the HTTP semantic conventions are declared stable, changes to the attributes in this section will only be allowed
 if they do not cause breaking changes to HTTP semantic conventions.
diff --git a/docs/general/naming.md b/docs/general/naming.md
@@ -139,7 +139,7 @@ no longer recommended, it SHOULD be deprecated.
   the following Unicode code points: Latin alphabet, Numeric, Underscore, Dot
   (as namespace delimiter).
 
-> Note:
+> [!Note]
 > Semantic Conventions tooling limits names to lowercase
 > Latin alphabet, Numeric, Underscore, Dot (as namespace delimiter).
 > Names must start with a letter, end with an alphanumeric character, and must not
diff --git a/docs/graphql/graphql-spans.md b/docs/graphql/graphql-spans.md
@@ -19,7 +19,7 @@ This span represents an incoming operation on a GraphQL server implementation.
 `graphql.operation.type` is available. If `graphql.operation.type` is not available,
 the span SHOULD be named `GraphQL Operation`.
 
-> **Warning**
+> [!WARNING]
 > The `graphql.operation.name` value is provided by the client and can have high
 > cardinality. Using it in the GraphQL server span name (by default) is
 > NOT RECOMMENDED.
diff --git a/docs/how-to-write-conventions/resource-and-entities.md b/docs/how-to-write-conventions/resource-and-entities.md
@@ -50,7 +50,8 @@ descriptive. See
 [How to define identifying attributes?](#how-to-define-identifying-attributes)
 for details on what these mean.
 
-> Note: Declaring Entity relationships is not yet supported.
+> [!Note]
+> Declaring Entity relationships is not yet supported.
 
 ### Declaring associations between signals
 
diff --git a/docs/http/README.md b/docs/http/README.md
@@ -10,7 +10,7 @@ This document defines semantic conventions for HTTP spans, metrics and logs.
 They can be used for http and https schemes
 and various HTTP versions like 1.1, 2 and SPDY.
 
-> **Warning**
+> [!IMPORTANT]
 > Existing HTTP instrumentations that are using
 > [v1.20.0 of this document](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.20.0/specification/trace/semantic_conventions/http.md)
 > (or prior):
diff --git a/docs/http/http-metrics.md b/docs/http/http-metrics.md
@@ -29,7 +29,7 @@ operations. By adding HTTP attributes to metric events it allows for finely tune
 
 <!-- tocstop -->
 
-> **Warning**
+> [!IMPORTANT]
 > Existing HTTP instrumentations that are using
 > [v1.20.0 of this document](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.20.0/specification/metrics/semantic_conventions/http-metrics.md)
 > (or prior):
@@ -144,12 +144,14 @@ support custom route formatting. Instrumentations SHOULD document the format and
 **[7] `network.protocol.version`:** If protocol version is subject to negotiation (for example using [ALPN](https://www.rfc-editor.org/rfc/rfc7301.html)), this attribute SHOULD be set to the negotiated version. If the actual protocol version is not known, this attribute SHOULD NOT be set.
 
 **[8] `server.address`:** See [Setting `server.address` and `server.port` attributes](/docs/http/http-spans.md#setting-serveraddress-and-serverport-attributes).
-> **Warning**
+
+> [!WARNING]
 > Since this attribute is based on HTTP headers, opting in to it may allow an attacker
 > to trigger cardinality limits, degrading the usefulness of the metric.
 
 **[9] `server.port`:** See [Setting `server.address` and `server.port` attributes](/docs/http/http-spans.md#setting-serveraddress-and-serverport-attributes).
-> **Warning**
+
+> [!WARNING]
 > Since this attribute is based on HTTP headers, opting in to it may allow an attacker
 > to trigger cardinality limits, degrading the usefulness of the metric.
 
@@ -233,12 +235,14 @@ Instrumentations for specific web frameworks that consider HTTP methods to be ca
 Tracing instrumentations that do so, MUST also set `http.request.method_original` to the original value.
 
 **[2] `server.address`:** See [Setting `server.address` and `server.port` attributes](/docs/http/http-spans.md#setting-serveraddress-and-serverport-attributes).
-> **Warning**
+
+> [!WARNING]
 > Since this attribute is based on HTTP headers, opting in to it may allow an attacker
 > to trigger cardinality limits, degrading the usefulness of the metric.
 
 **[3] `server.port`:** See [Setting `server.address` and `server.port` attributes](/docs/http/http-spans.md#setting-serveraddress-and-serverport-attributes).
-> **Warning**
+
+> [!WARNING]
 > Since this attribute is based on HTTP headers, opting in to it may allow an attacker
 > to trigger cardinality limits, degrading the usefulness of the metric.
 
@@ -347,12 +351,14 @@ support custom route formatting. Instrumentations SHOULD document the format and
 **[7] `network.protocol.version`:** If protocol version is subject to negotiation (for example using [ALPN](https://www.rfc-editor.org/rfc/rfc7301.html)), this attribute SHOULD be set to the negotiated version. If the actual protocol version is not known, this attribute SHOULD NOT be set.
 
 **[8] `server.address`:** See [Setting `server.address` and `server.port` attributes](/docs/http/http-spans.md#setting-serveraddress-and-serverport-attributes).
-> **Warning**
+
+> [!WARNING]
 > Since this attribute is based on HTTP headers, opting in to it may allow an attacker
 > to trigger cardinality limits, degrading the usefulness of the metric.
 
 **[9] `server.port`:** See [Setting `server.address` and `server.port` attributes](/docs/http/http-spans.md#setting-serveraddress-and-serverport-attributes).
-> **Warning**
+
+> [!WARNING]
 > Since this attribute is based on HTTP headers, opting in to it may allow an attacker
 > to trigger cardinality limits, degrading the usefulness of the metric.
 
@@ -480,12 +486,14 @@ support custom route formatting. Instrumentations SHOULD document the format and
 **[7] `network.protocol.version`:** If protocol version is subject to negotiation (for example using [ALPN](https://www.rfc-editor.org/rfc/rfc7301.html)), this attribute SHOULD be set to the negotiated version. If the actual protocol version is not known, this attribute SHOULD NOT be set.
 
 **[8] `server.address`:** See [Setting `server.address` and `server.port` attributes](/docs/http/http-spans.md#setting-serveraddress-and-serverport-attributes).
-> **Warning**
+
+> [!WARNING]
 > Since this attribute is based on HTTP headers, opting in to it may allow an attacker
 > to trigger cardinality limits, degrading the usefulness of the metric.
 
 **[9] `server.port`:** See [Setting `server.address` and `server.port` attributes](/docs/http/http-spans.md#setting-serveraddress-and-serverport-attributes).
-> **Warning**
+
+> [!WARNING]
 > Since this attribute is based on HTTP headers, opting in to it may allow an attacker
 > to trigger cardinality limits, degrading the usefulness of the metric.
 
diff --git a/docs/http/http-spans.md b/docs/http/http-spans.md
@@ -34,7 +34,7 @@ and various HTTP versions like 1.1, 2 and SPDY.
 
 <!-- tocstop -->
 
-> **Warning**
+> [!IMPORTANT]
 > Existing HTTP instrumentations that are using
 > [v1.20.0 of this document](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.20.0/specification/trace/semantic_conventions/http.md)
 > (or prior):
@@ -405,7 +405,8 @@ HTTP server instrumentations SHOULD do the best effort when populating `server.a
 * The [`:authority`][HTTP/2 authority] pseudo-header in case of HTTP/2 or HTTP/3
 * The [`Host`][Host header] header.
 
-> **Note**: The `Host` and `:authority` headers contain host and port number of the server. The same applies to the `host` identifier of `Forwarded` header or the `X-Forwarded-Host` header. Instrumentations SHOULD populate both `server.address` and `server.port` attributes by parsing the value of corresponding header.
+> [!NOTE]
+> The `Host` and `:authority` headers contain host and port number of the server. The same applies to the `host` identifier of `Forwarded` header or the `X-Forwarded-Host` header. Instrumentations SHOULD populate both `server.address` and `server.port` attributes by parsing the value of corresponding header.
 
 Application developers MAY overwrite potentially inaccurate values of `server.*` attributes using a [SpanProcessor][SpanProcessor] and MAY capture private host information using applicable [resource attributes](/docs/resource/README.md).
 
diff --git a/docs/messaging/README.md b/docs/messaging/README.md
@@ -8,7 +8,7 @@ linkTitle: Messaging
 
 This document defines semantic conventions for messaging systems spans, metrics and logs.
 
-> [!Warning]
+> [!IMPORTANT]
 >
 > Existing messaging instrumentations that are using
 > [v1.24.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.24.0/docs/messaging/messaging-spans.md)
diff --git a/docs/messaging/azure-messaging.md b/docs/messaging/azure-messaging.md
@@ -8,7 +8,7 @@ linkTitle: Azure
 
 The Semantic Conventions for [Azure Service Bus](https://learn.microsoft.com/azure/service-bus-messaging/service-bus-messaging-overview) and [Azure Event Hubs](https://learn.microsoft.com/azure/event-hubs/event-hubs-about) extend and override the [Messaging Semantic Conventions](README.md).
 
-> [!Warning]
+> [!IMPORTANT]
 >
 > Existing messaging instrumentations that are using
 > [v1.24.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.24.0/docs/messaging/messaging-spans.md)
diff --git a/docs/messaging/gcp-pubsub.md b/docs/messaging/gcp-pubsub.md
@@ -8,7 +8,7 @@ linkTitle: Google Cloud Pub/Sub
 
 The Semantic Conventions for [Google Cloud Pub/Sub](https://cloud.google.com/pubsub) extend and override the [Messaging Semantic Conventions](README.md).
 
-> [!Warning]
+> [!IMPORTANT]
 >
 > Existing messaging instrumentations that are using
 > [v1.24.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.24.0/docs/messaging/messaging-spans.md)
diff --git a/docs/messaging/kafka.md b/docs/messaging/kafka.md
@@ -16,7 +16,7 @@ linkTitle: Kafka
 
 The Semantic Conventions for [Apache Kafka](https://kafka.apache.org/) extend and override the [Messaging Semantic Conventions](README.md).
 
-> [!Warning]
+> [!IMPORTANT]
 >
 > Existing messaging instrumentations that are using
 > [v1.24.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.24.0/docs/messaging/messaging-spans.md)
diff --git a/docs/messaging/messaging-metrics.md b/docs/messaging/messaging-metrics.md
@@ -18,7 +18,7 @@ linkTitle: Metrics
 
 <!-- tocstop -->
 
-> [!Warning]
+> [!IMPORTANT]
 >
 > Existing messaging instrumentations that are using
 > [v1.24.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.24.0/docs/messaging/messaging-spans.md)
diff --git a/docs/messaging/messaging-spans.md b/docs/messaging/messaging-spans.md
@@ -39,7 +39,7 @@ linkTitle: Spans
 
 <!-- tocstop -->
 
-> [!Warning]
+> [!IMPORTANT]
 >
 > Existing messaging instrumentations that are using
 > [v1.24.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.24.0/docs/messaging/messaging-spans.md)
diff --git a/docs/messaging/rabbitmq.md b/docs/messaging/rabbitmq.md
@@ -8,7 +8,7 @@ linkTitle: RabbitMQ
 
 The Semantic Conventions for [RabbitMQ](https://www.rabbitmq.com/) extend and override the [Messaging Semantic Conventions](README.md).
 
-> [!Warning]
+> [!IMPORTANT]
 >
 > Existing messaging instrumentations that are using
 > [v1.24.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.24.0/docs/messaging/messaging-spans.md)
diff --git a/docs/messaging/rocketmq.md b/docs/messaging/rocketmq.md
@@ -8,7 +8,7 @@ linkTitle: RocketMQ
 
 The Semantic Conventions for [Apache RocketMQ](https://rocketmq.apache.org/) extend and override the [Messaging Semantic Conventions](README.md).
 
-> [!Warning]
+> [!IMPORTANT]
 >
 > Existing messaging instrumentations that are using
 > [v1.24.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.24.0/docs/messaging/messaging-spans.md)
diff --git a/docs/non-normative/code-generation.md b/docs/non-normative/code-generation.md
@@ -31,7 +31,7 @@ Possible solutions include:
 - Follow language-specific conventions to annotate unstable parts. For example, Semantic Conventions in Python puts unstable attributes in `opentelemetry.semconv._incubating` import path which is considered (following Python underscore convention) to be internal and subject to change.
 - Ship two different artifacts: one that contains stable Semantic Conventions and another one with all available conventions. For example, [semantic-conventions in Java](https://github.com/open-telemetry/semantic-conventions-java) are shipped in two artifacts: `opentelemetry-semconv` and `opentelemetry-semconv-incubating`.
 
-> Note:
+> [!Note]
 > Shipping two versions of the same artifact (stable and preview) could be problematic due to diamond-dependency problems.
 > For example, if user application depends on the `semconv v1.0.0-preview` and some library brings transitive dependency on `semconv v1.1.0` that does not contain
 > experimental conventions, the latter would be resolved leading to compilation or runtime issues in the application.
diff --git a/docs/rpc/README.md b/docs/rpc/README.md
@@ -9,7 +9,7 @@ linkTitle: RPC
 This document defines semantic conventions for remote procedure calls (RPC)
 , also called "remote method invocations" (RMI).
 
-> **Warning**
+> [!IMPORTANT]
 > Existing RPC instrumentations that are using
 > [v1.37.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.37.0/docs/rpc/README.md)
 > (or prior):
diff --git a/docs/rpc/rpc-metrics.md b/docs/rpc/rpc-metrics.md
@@ -27,7 +27,7 @@ metrics can be filtered for finer grain analysis.
 
 <!-- tocstop -->
 
-> **Warning**
+> [!IMPORTANT]
 > Existing RPC instrumentations that are using
 > [v1.37.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.37.0/docs/rpc/rpc-metrics.md)
 > (or prior):
diff --git a/docs/rpc/rpc-spans.md b/docs/rpc/rpc-spans.md
diff --git a/docs/system/process-metrics.md b/docs/system/process-metrics.md
diff --git a/docs/system/system-metrics.md b/docs/system/system-metrics.md
diff --git a/model/graphql/spans.yml b/model/graphql/spans.yml
diff --git a/model/http/metrics.yaml b/model/http/metrics.yaml

Original file line number	Diff line number	Diff line change
`@@ -10,7 +10,7 @@ aliases: [/docs/specs/semconv/database]`
`10`	`10`	`This document defines semantic conventions for database client spans as well as`
`11`	`11`	`database metrics and logs.`
`12`	`12`
`13`		`-> Warning`
	`13`	`+> [!IMPORTANT]`
`14`	`14`	`>`
`15`	`15`	`> Existing database instrumentations that are using`
`16`	`16`	`> [v1.24.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.24.0/docs/database/database-spans.md)`
Original file line number	Diff line number	Diff line change
`@@ -27,7 +27,7 @@ aliases: [/docs/specs/semconv/database/database-metrics.md]`
`27`	`27`
`28`	`28`	`<!-- tocstop -->`
`29`	`29`
`30`		`-> Warning`
	`30`	`+> [!IMPORTANT]`
`31`	`31`	`>`
`32`	`32`	`> Existing database instrumentations that are using`
`33`	`33`	`> [v1.24.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.24.0/docs/database/database-spans.md)`
Original file line number	Diff line number	Diff line change
`@@ -20,7 +20,7 @@ aliases: [/docs/specs/semconv/database/database-spans.md]`
`20`	`20`
`21`	`21`	`<!-- tocstop -->`
`22`	`22`
`23`		`-> Warning`
	`23`	`+> [!IMPORTANT]`
`24`	`24`	`>`
`25`	`25`	`> Existing database instrumentations that are using`
`26`	`26`	`> [v1.24.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.24.0/docs/database/database-spans.md)`
Original file line number	Diff line number	Diff line change
`@@ -6,7 +6,7 @@ linkTitle: Generative AI`
`6`	`6`
`7`	`7`	`Status: [Development][DocumentStatus]`
`8`	`8`
`9`		`-> [!Warning]`
	`9`	`+> [!IMPORTANT]`
`10`	`10`	`>`
`11`	`11`	`> Existing GenAI instrumentations that are using`
`12`	`12`	`> [v1.36.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.36.0/docs/gen-ai/README.md)`
Original file line number	Diff line number	Diff line change
`@@ -6,7 +6,7 @@ linkTitle: AWS Bedrock`
`6`	`6`
`7`	`7`	`Status: [Development][DocumentStatus]`
`8`	`8`
`9`		`-> [!Warning]`
	`9`	`+> [!IMPORTANT]`
`10`	`10`	`>`
`11`	`11`	`> Existing GenAI instrumentations that are using`
`12`	`12`	`> [v1.36.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.36.0/docs/gen-ai/README.md)`
Original file line number	Diff line number	Diff line change
`@@ -15,7 +15,7 @@ linkTitle: Azure AI Inference`
`15`	`15`
`16`	`16`	`<!-- tocstop -->`
`17`	`17`
`18`		`-> [!Warning]`
	`18`	`+> [!IMPORTANT]`
`19`	`19`	`>`
`20`	`20`	`> Existing GenAI instrumentations that are using`
`21`	`21`	`> [v1.36.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.36.0/docs/gen-ai/README.md)`
Original file line number	Diff line number	Diff line change
`@@ -15,7 +15,7 @@ linkTitle: Agent spans`
`15`	`15`
`16`	`16`	`<!-- tocstop -->`
`17`	`17`
`18`		`-> [!Warning]`
	`18`	`+> [!IMPORTANT]`
`19`	`19`	`>`
`20`	`20`	`> Existing GenAI instrumentations that are using`
`21`	`21`	`> [v1.36.0 of this document](https://github.com/open-telemetry/semantic-conventions/blob/v1.36.0/docs/gen-ai/README.md)`