update prisma:engine to prisma:engine:query

content/200-orm/200-prisma-client/600-observability-and-logging/250-opentelemetry-tracing.mdx

@@ -34,7 +34,7 @@ For each trace, Prisma Client outputs a series of spans. The number and type of
 - `prisma:client:operation`: Represents the entire Prisma Client operation, from Prisma Client to the database and back. It contains details such as the model and method called by Prisma Client. Depending on the Prisma operation, it contains one or more of the following spans:
   - `prisma:client:connect`: Represents how long it takes for Prisma Client to connect to the database.
   - `prisma:client:serialize`: Represents how long it takes to validate and transform a Prisma Client operation into a query for the [query engine](/orm/more/under-the-hood/engines).
-  - `prisma:engine`: Represents how long a query takes in the query engine.
+  - `prisma:engine:query`: Represents how long a query takes in the query engine.
     - `prisma:engine:connection`: Represents how long it takes for Prisma Client to get a database connection.
     - `prisma:engine:db_query`: Represents the database query that was executed against the database. It includes the query in the tags, and how long the query took to run.
     - `prisma:engine:serialize`: Represents how long it takes to transform a database query result into a Prisma Client result.
@@ -56,7 +56,7 @@ The trace is structured as follows:
 
 - `prisma:client:operation`
   - `prisma:client:serialize`
-  - `prisma:engine`
+  - `prisma:engine:query`
     - `prisma:engine:connection`
     - `prisma:engine:db_query`: details of the first SQL query or command...
     - `prisma:engine:db_query`: ...details of the next SQL query or command...