fix(semconv): update database semantic conventions link for blog posts

Signed-off-by: Vitor Vasconcellos <[email protected]>

Author: vitorvasc

content-modules/semantic-conventions

@@ -71,9 +71,8 @@ Examples include:
   inherently structured
 - **GraphQL** — responses may include
   [lists of structured errors](https://graphql.org/learn/response/#errors)
-- **[Database operations](https://github.com/open-telemetry/semantic-conventions/blob/v1.38.0/docs/database/database-spans.md)**
-  — batch operations have properties that flat attributes cannot adequately
-  capture
+- **[Database operations](https://github.com/open-telemetry/semantic-conventions/blob/v1.38.0/docs/database/database-metrics.md)** — batch
+  operations have properties that flat attributes cannot adequately capture
 
 Before extending support for complex attributes to all signals, we explored
 several alternatives:

content/en/blog/2025/complex-attribute-types.md

@@ -125,7 +125,7 @@ This supports context propagation between database client and server when
 database log records are enabled. For more information, see:
 
 - [OpenTelemetry Python sqlcommenter example](https://github.com/open-telemetry/opentelemetry-python/tree/main/docs/examples/sqlcommenter/)
-- [Semantic Conventions - Database Spans](/docs/specs/semconv/database/database-spans/#sql-commenter)
+- [Semantic Conventions - Database Spans](/docs/specs/semconv/db/database-spans/#sql-commenter)
 - [sqlcommenter](https://google.github.io/sqlcommenter/)
 
 ## Next steps