Style and grammar tweak

pages/DSNP/Identity.md

@@ -29,14 +29,14 @@ An implementation MUST NOT allow the user to remove the only or last remaining c
 
 A user may choose to retire their Identifier at any time.
 Once an Identifier is retired, an implementation MAY remove all state data associated with that Identifier, provided that an indication that the Identifier is retired remains, so it may not be reused in the future.
-This means that all data previously sent from the Identifier, the keys associated with the Identifier, any user data (see below) associated with the identifier, and the delegations (see next section) associated with the Identifier may be removed.
+This means that all data previously sent from the Identifier, the keys associated with the Identifier, any user data (see below) associated with the Identifier, and the delegations (see next section) associated with the Identifier may be removed.
 
 After an Identifier is retired, any existing or future [Announcements](Announcements.md) from the Identifier should be treated as if they have been [tombstoned](Types/Tombstone.md) (for Announcement Types that support tombstoning).
 A retired Identifier MUST NOT be allowed to act as a principal for any additional DSNP [Operations](Operations.md).
 
 ## Delegation
 
-* A user MUST be able to delegate and revoke permissions to other parties to submit each type of announcements or replace each type of user data on their behalf.
+* A user MUST be able to delegate and revoke permissions to other parties to submit each type of announcement or replace each type of user data on their behalf.
 * A user MUST be able to revoke delegated permissions.
 * Announcements and user data updates from a delegate MUST be able to be verified as to which delegate was responsible for the action.
 * Delegation revocation MUST NOT be retroactive.