Apply edits suggested in PR #1242 review

See #1242 (review)

index.bs

@@ -456,8 +456,7 @@ In this flow, the [=[WRP]=] does not have a preference for [=platform authentica
 
 1. The [=client=] connects to the authenticator, performing any pairing actions if necessary.
 
-1. The authenticator shows appropriate UI for the user to select the authenticator on which the new credential will be
-    created, and obtains a biometric or other authorization gesture from the user.
+1. The authenticator shows appropriate UI for the user to provide a biometric or other authorization gesture.
 
 1. The authenticator returns a response to the [=client=], which in turn returns a response to the [=[RP]=] script. If
     the user declined to select an authenticator or provide authorization, an appropriate error is returned.
@@ -533,10 +532,7 @@ a [=user-verifying platform authenticator=].
 
     1. The user agent checks if a [=user-verifying platform authenticator=] is available. If not, terminate this flow.
 
-    1. The [=[RP]=] asks the user if they want to create a credential with it.
-
-    1. If no [=user-verifying platform authenticator=] is available,
-        or if the user does not want to create a credential, terminate this flow.
+    1. The [=[RP]=] asks the user if they want to create a credential with it. If not, terminate this flow.
 
     1. The user agent and/or operating system shows appropriate UI and guides the user in creating a credential
         using one of the available platform authenticators.
@@ -708,7 +704,7 @@ handled on the server side and do not need support from the API specified here.
     * User goes to server.example.net, authenticates and follows a link to report a lost/stolen [=authenticator=].
     * Server returns a page showing the list of registered credentials with friendly names as configured during registration.
     * User selects a credential and the server deletes it from its database.
-    * In future, the [=[RP]=] script does not specify this credential in any list of acceptable credentials, and assertions
+    * In the future, the [=[RP]=] script does not specify this credential in any list of acceptable credentials, and assertions
         signed by this credential are rejected.
 
 - Possibility #2 -- server deregisters the credential due to inactivity.