Update attribution_scopes.md - updating grammatical error (#1419)

updating grammatical error
WICG · Sep 6, 2024 · d7f363f · d7f363f
1 parent 82b5004
commit d7f363f
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/attribution_scopes.md b/attribution_scopes.md
@@ -91,7 +91,7 @@ If the trigger registration's `attribution_scopes` is empty, then all sources ar
 
 Once a `attribution scopes/limit` is set, the last K values (where K = `attribution scopes/limit`) of `attribution_scopes/values` will be considered the final set of attribution scopes values and any source with additional values will be deleted. Additionally, when a new source uses the `attribution_scopes` feature, then all previous source registrations that do no use the feature will be deleted. Similarly, if a new source does not use the `attribution_scopes` feature, then all previous pending sources registrations will be treated as if they have empty `attribution_scopes` fields.
 
-For sources that use the `attribution_scopes` feature, if the source registration is specified with a configuration that has a higher number of event states than the most recent `max_event_states` for the same reporting origin, then the source will be rejected and the registration will fail. , if the `max_event_states` field is changed in a future source registration, then all other previous pending source registrations that use the `attribution_scopes` feature with a different `max_event_states` will be ignored in subsequent attribution report generation flows, but will still count towards rate limits. 
+For sources that use the `attribution_scopes` feature, if the source registration is specified with a configuration that has a higher number of event states than the most recent `max_event_states` for the same reporting origin, then the source will be rejected and the registration will fail. If the `max_event_states` field is changed in a future source registration, then all other previous pending source registrations that use the `attribution_scopes` feature with a different `max_event_states` will be ignored in subsequent attribution report generation flows, but will still count towards rate limits. 
 
 ### Updating attribution scope values