fix(develop): Clearer wording for attrs on current scope (#15866)

Author: sentrivana

develop-docs/sdk/telemetry/scopes.mdx

@@ -98,7 +98,7 @@ The method SHOULD accept a dictionary/map/object where:
 
 - Attributes set on the global scope MUST be applied to all logs and metrics
 - Attributes set on the isolation scope MUST be applied to all logs and metrics in that execution context
-- Attributes set on the current scope MUST be applied only to the current log and current metric
+- Attributes set on the current scope MUST be applied only to the logs and metrics that are captured while that current scope is active
 - When the same attribute key exists in multiple scopes, the more specific scope's value takes precedence (current > isolation > global)
 - When the same attribute key exists on the current log or metric, it MUST take precedence over an attribute with the same key set on any scope (log/metric > current > isolation > global)
 - The SDK SHOULD keep the attribute format consistent with the user-set format until user-provided processing callbacks like `before_send_log` have been called. This ensures compatibility with already existing callbacks and avoids unexpected changes to the attribute format.