Link “assertion”, as requested by Jeff.

index.bs

@@ -1173,7 +1173,7 @@ When this method is invoked, the user agent MUST execute the following algorithm
     1. Let |userPresence| be a Boolean value set to the inverse of |userVerification|.
 
     1. <span id="allowCredentialDescriptorListCreation"></span>
-       If <code>|options|.{{PublicKeyCredentialRequestOptions/allowCredentials}}</code>
+        If <code>|options|.{{PublicKeyCredentialRequestOptions/allowCredentials}}</code>
         <dl class="switch">
             :   [=list/is not empty=]
             ::  1. Let |allowCredentialDescriptorList| be a new [=list=].
@@ -3544,7 +3544,7 @@ These are recommended for implementation by user agents targeting broad interope
 ## FIDO AppID Extension (appid) ## {#sctn-appid-extension}
 
 This [=client extension=] allows [=[RPS]=] that have previously registered a
-credential using the legacy FIDO JavaScript APIs to request an assertion. The
+credential using the legacy FIDO JavaScript APIs to request an [=assertion=]. The
 FIDO APIs use an alternative identifier for [=relying parties=] called an |AppID|
 [[FIDO-APPID]], and any credentials created using those APIs will be bound to
 that identifier. Without this extension they would need to be re-registered in