Address review comments

See #956 (review)

index.bs

@@ -2454,15 +2454,15 @@ transport protocols are referred to as <dfn>roaming authenticators</dfn>.
 
 Some [=platform authenticators=] could possibly also act as [=roaming authenticators=] depending on context. For example, a
 [=platform authenticator=] integrated into a mobile device could make itself available as a [=roaming authenticator=] via
-Bluetooth. In this case the [=client=] would identify it only as a [=roaming authenticator=], and not as a [=platform
+Bluetooth. In this case the [=client=] would recognize it only as a [=roaming authenticator=], and not as a [=platform
 authenticator=].
 
-The primary use case for [=platform authenticators=] is to register a particular [=client device=] as a "trusted device" available
+A primary use case for [=platform authenticators=] is to register a particular [=client device=] as a "trusted device" available
 as a [=something you have=] [=authentication factor=] for future [=authentication=]. This gives the user the convenience benefit
 of not needing a [=roaming authenticator=] for future [=authentication ceremonies=], e.g., the user will not have to dig around in
 their pocket for their key fob or phone.
 
-The primary use case for [=roaming authenticators=] is for initial [=authentication=] on a new [=client device=], or on [=client
+A primary use case for [=roaming authenticators=] is for initial [=authentication=] on a new [=client device=], or on [=client
 devices=] that are rarely used or do not include a [=platform authenticator=]; or when policy or preference dictates that the
 [=authenticator=] be kept separate from the [=clients=] it is used with. A [=roaming authenticator=] can also be used to hold
 backup [=public key credential|credentials=] in case another [=authenticator=] is lost.