diff --git a/proposals/20231220-features-adoption-and-deprecation.md b/proposals/20231220-features-adoption-and-deprecation.md
index cb18626d..cdfdddb1 100644
--- a/proposals/20231220-features-adoption-and-deprecation.md
+++ b/proposals/20231220-features-adoption-and-deprecation.md
@@ -114,7 +114,7 @@ Maturation levels (inspired by those we already have in place for [repositories]
 The adoption policy applies to any backward compatible user-facing changes which add functionalities. For non-backward compatible changes see the [deprecation policy](#Deprecation-policy) below.
 
 **Adoption rules**:
-1. A feature can be introduced at any level at only one of the following levels:
+1. A feature can be introduced at only one of the following levels:
    - Sandbox: The feature must be opt-in (e.g., a feature flag), labeled as *Sandbox* and the user must be proactively informed by the experimental nature of the feature (i.e. emitting a notice when the feature is being enabled).
    - Incubating: The feature must be labeled as *Incubating*.
 2. A feature can be promoted *from Sandbox to Incubating* or *from Incubating to Stable* only after at least one release cycle has passed without user-facing changes to the feature.