Merge pull request #201 from w3c/jeffh-editorial-cleanups

various editorial cleanups

index.bs

@@ -24,6 +24,7 @@ Text Macro: RPS Relying Parties
 Text Macro: INFORMATIVE <em>This section is not normative.</em>
 Text Macro: WAC WebAuthn Client
 Ignored Vars: op, alg, type, algorithm
+Issue Tracking: Github https://github.com/w3c/webauthn/issues
 Abstract: This specification defines an API enabling the creation and use of strong, attested, cryptographic scoped credentials 
  by web applications, for the purpose of strongly authenticating users. Conceptually, one or more credentials, each scoped to a
  given Relying Party, are created and stored on an authenticator by the user agent in conjunction with the web application. The
@@ -2038,14 +2039,14 @@ credential. It is intended primarily for [RPS] that wish to tightly control the
 
     Each data item is in turn a CBOR array of length 3 (type 0x83) with the following data items:
     - Data Item 1 – User Verification Method. This is the authentication method/factor used by the authenticator to verify 
-                    the user. Available values are defined in the FIDO Registry of Predefined Values, ‘User Verification 
-                    Methods’ section. It is encoded as a CBOR unsigned integer (Major type 0).
+                    the user. Available values are defined in [[!FIDOReg]], "User Verification Methods" section. It is 
+                    encoded as a CBOR unsigned integer (Major type 0).
     - Data Item 2 – Key Protection Type. This is the method used by the authenticator to protect the FIDO registration 
-                    private key material. Available values are defined in the FIDO Registry of Predefined Values, ‘Key 
-                    Protection Types’ section. It is encoded as a CBOR 2 byte unsigned short (Major type 0).
+                    private key material. Available values are defined in [[!FIDOReg]], "Key Protection Types" section. 
+                    It is encoded as a CBOR 2 byte unsigned short (Major type 0).
     - Data Item 3 – Matcher Protection Type. This is the method used by the authenticator to protect the matcher that 
-		    performs user verification. Available values are defined in the FIDO Registry of Predefined Values, 
-		    ‘Matcher Protection Types’ section. It is encoded as a CBOR 2 byte unsigned short (Major type 0).
+		            performs user verification. Available values are defined in [[!FIDOReg]], "Matcher Protection Types" 
+		            section. It is encoded as a CBOR 2 byte unsigned short (Major type 0).
 
     This is repeated for each factor used in the authentication instance.
 
@@ -2336,7 +2337,8 @@ handled on the server side and do not need support from the API specified here.
 
 
 # Acknowledgements # {#acknowledgements}
-We thank the following for their contributions to, and thorough review of, this specification: Jing Jin and Giridhar Mandyam.
+We thank the following for their contributions to, and thorough review of, this specification: Domenic Denicola, Rahul Ghosh,
+Brad Hill, Jing Jin, Anne van Kesteren, Giridhar Mandyam, Axel Nennker, Yaron Sheffer, Mike West.
 
 <pre class=biblio>
 {  
@@ -2451,6 +2453,13 @@ We thank the following for their contributions to, and thorough review of, this
     "title": "FIDO Security Reference",
     "href": "https://fidoalliance.org/specs/fido-uaf-v1.0-ps-20141208/fido-security-ref-v1.0-ps-20141208.html",
     "status": "FIDO Alliance Proposed Standard"
+  },
+
+  "FIDOReg": {
+    "authors": ["R. Lindemann", "D. Baghdasaryan", "B. Hill"],
+    "title": "FIDO UAF Registry of Predefined Values",
+    "href": "https://fidoalliance.org/specs/fido-uaf-v1.0-ps-20141208/fido-uaf-reg-v1.0-ps-20141208.html",
+    "status": "FIDO Alliance Proposed Standard"
   }
 }
 </pre>