update db.collection.name note

docs/database/cosmosdb.md

@@ -43,8 +43,6 @@ Cosmos DB instrumentation includes call-level (public API) surface spans and net
 | [`db.query.parameter.<key>`](/docs/attributes-registry/db.md) | string | A query parameter used in `db.query.text`, with `<key>` being the parameter name, and the attribute value being a string representation of the parameter value. [12] | `someval`; `55` | `Opt-In` | ![Experimental](https://img.shields.io/badge/-experimental-blue) |
 
 **[1]:** It is RECOMMENDED to capture the value as provided by the application without attempting to do any case normalization.
-If the collection name is parsed from the query text, it SHOULD be the first collection name found in the query and it SHOULD match the value provided in the query text including any schema and database name prefix.
-For batch operations, if the individual operations are known to have the same collection name then that collection name SHOULD be used, otherwise `db.collection.name` SHOULD NOT be captured.
 
 **[2]:** if not `gateway` (the default value is assumed to be `gateway`).
 

model/trace/database.yaml

@@ -362,6 +362,8 @@ groups:
       - ref: db.collection.name
         brief: >
           Cosmos DB container name.
+        note: >
+          It is RECOMMENDED to capture the value as provided by the application without attempting to do any case normalization.
         requirement_level:
           conditionally_required: if available
       - ref: db.cosmosdb.request_content_length