Improve wording on MetricReader/SDK

[reyang]

This is to follow up the non-blocking comment #2404 (comment).

Discussed during the 3/18/2022 triage meeting, we consider this as a nice wording change which doesn't block #2404.

[tigrannajaryan]

@reyang I just noticed this is assigned to myself. I will reassign this to you if you don't mind (following the process here).

[ocelotl]

I asked Claude to review this issue and Claude suggests it be closed with this explanation:

A non-blocking editorial follow-up to already-merged PR #2404 (merged 2022-03-18), explicitly triaged as 'a nice wording change which doesn't block #2404' with no concrete text proposed. It fizzled: the only later comment (2022-04-20) was a reassignment nudge from tigrannajaryan, no closing PR, dead since. Low-value abandoned editorial item.

To guard against a mistaken suggestion, Claude then independently re-verified this conclusion:

Non-blocking editorial nit on wording flagged in PR #2404; the MetricReader/temporality section was rewritten multiple times since 2022 and now states the MUST-normative conversion behavior explicitly (sdk.md L1367-1374), so the original ambiguity is moot/superseded — closeable, better labeled obsolete than merely abandoned.

Claude evaluated this issue with medium confidence that it can be closed.

Claude has classified this issue as obsolete.

The intention of this comment is to make it easier for a human being to review this issue before making a decision.

[svrnm]

Closing this issue, it was discussed, no conclusion found and stalled. If you think this topic should be discussed again, reopen or raise a new issue.