@@ -30,6 +30,10 @@ sidebar_order: 3
 
 SDKs can track feature flag evaluations and attach them to error events and spans, so users can see which flags were in effect when an error happened or a span ran.
 
+## Scope
+
+This spec applies to SDKs that track feature flag evaluations. Tracking evaluations is optional.
+
 ## Definitions
 
 - **Evaluation**: a flag name and the boolean result it evaluated to.
@@ -41,8 +45,6 @@ SDKs can track feature flag evaluations and attach them to error events and span
 
 ### Tracking Feature Flag Evaluations
 
-SDKs **MAY** track evaluations. The remaining requirements in this spec apply only to SDKs that do.
-
 **Error events.** Evaluations recorded on a scope **SHOULD** be attached to error events captured with that scope. Attached evaluations **MUST** follow the [Feature Flag Context](/sdk/foundations/envelopes/event-payloads/contexts/#feature-flag-context) schema. An event **SHOULD** contain only the latest evaluation of each flag, and only for the 100 most recently evaluated flags.
 
 When a scope is forked, events captured with the new scope **SHOULD** include the evaluations recorded on the original scope before the fork. Evaluations recorded on the new scope **SHOULD NOT** appear in events captured with the original scope.