Updates

Author: msmbaldwin

articles/attestation/claim-sets.md

@@ -12,15 +12,15 @@ ms.author: mbaldwin
 ---
 # Claim sets
 
-Claims generated in the process of attesting enclaves using Microsoft Azure Attestation can be divided into the below categories:
+Claims generated in the process of attesting enclaves using Microsoft Azure Attestation can be divided into these categories:
 
 - **Incoming claims**: The claims generated by Microsoft Azure Attestation after parsing the attestation evidence and can be used by policy authors to define authorization rules in a custom policy
 
 - **Outgoing claims**: The claims generated by Azure Attestation and included in the attestation token
 
 - **Property claims**: The claims created as an output by Azure Attestation. It contains all the claims that represent properties of the attestation token, such as encoding of the report, validity duration of the report, and so on.
 
-## Incoming claims 
+## Incoming claims
 
 ### SGX attestation
 
@@ -42,7 +42,7 @@ Claims to be used by policy authors to define authorization rules in an SGX atte
 
   When an enclave author prefers to rotate MRSIGNER for security reasons, Azure Attestation policy must be updated to support the new and old MRSIGNER values before the binaries are updated. Otherwise authorization checks will fail resulting in attestation failures.
 
-  Attestation policy must be updated using the below format. 
+  Attestation policy must be updated using the format below.
 
   #### Before key rotation
 
@@ -87,10 +87,10 @@ Claims to be used by policy authors to define authorization rules in an SGX atte
 
   The enclave author assigns a Security Version Number (SVN) to each version of the SGX enclave. When a security issue is discovered in the enclave code, enclave author increments the SVN value post vulnerability fix. To prevent interacting with insecure enclave code, customers can add a validation rule in the attestation policy. If the SVN of the enclave code does not match the version recommended by the  enclave author, attestation will fail.
 
-Below claims are considered deprecated but are fully supported and will continue to be included in the future. It is recommended to use the non-deprecated claim names.
+These claims are considered deprecated but are fully supported and will continue to be included in the future. It is recommended to use the non-deprecated claim names:
 
 Deprecated claim | Recommended claim
---- | --- 
+--- | ---|
 $is-debuggable | x-ms-sgx-is-debuggable
 $product-id | x-ms-sgx-product-id
 $sgx-mrsigner | x-ms-sgx-mrsigner
@@ -114,7 +114,7 @@ Claims to be used by policy authors to define authorization rules in a TPM attes
 
 ### VBS attestation
 
-In addition to the TPM attestation policy claims, below claims can be used by policy authors to define authorization rules in a VBS attestation policy.
+In addition to the TPM attestation policy claims, these claims can be used by policy authors to define authorization rules in a VBS attestation policy:
 
 - **enclaveAuthorId**:  String value containing the Base64Url encoded value of the enclave author id-The author identifier of the primary module for the enclave
 - **enclaveImageId**:  String value containing the Base64Url encoded value of the enclave Image id-The image identifier of the primary module for the enclave
@@ -124,11 +124,11 @@ In addition to the TPM attestation policy claims, below claims can be used by po
 - **enclavePlatformSvn**:  Integer value containing the security version number of the platform that hosts the enclave
 - **enclaveFlags**:  The enclaveFlags claim is an Integer value containing Flags that describe the runtime policy for the enclave
 
-## Outgoing claims 
+## Outgoing claims
 
 ### Common for all attestation types
 
-Azure Attestation includes the below claims in the attestation token for all attestation types. 
+Azure Attestation includes these claims in the attestation token for all attestation types:
 
 - **x-ms-ver**: JWT schema version (expected to be "1.0")
 - **x-ms-attestation-type**: String value representing attestation type 
@@ -145,7 +145,7 @@ Below claim names are used from [IETF JWT specification](https://tools.ietf.org/
 - **"exp" (Expiration Time) Claim** - Expiration time after which the JWT must not be accepted for processing
 - **"nbf" (Not Before) Claim** - Not Before time before which the JWT must not be accepted for processing 
 
-Below claim names are used from [IETF EAT draft specification](https://tools.ietf.org/html/draft-ietf-rats-eat-03#page-9)
+These claim names are used from [IETF EAT draft specification](https://tools.ietf.org/html/draft-ietf-rats-eat-03#page-9):
 
 - **"Nonce claim" (nonce)** - An untransformed direct copy of an optional nonce value provided by a client 
 
@@ -162,7 +162,7 @@ rp_data  | nonce
 
 ### SGX attestation 
 
-Below claims are generated and included in the attestation token by the service for SGX attestation.
+These caims are generated and included in the attestation token by the service for SGX attestation:
 
 - **x-ms-sgx-is-debuggable**: A Boolean, which indicates whether or not the enclave has debugging enabled or not
 - **x-ms-sgx-product-id**: Product ID value of the SGX enclave 
@@ -180,17 +180,17 @@ Below claims are generated and included in the attestation token by the service
     - **tcbinfohash**: SHA256 value of the TCB Info collateral 
 - **x-ms-sgx-report-data**: SGX enclave report data field (usually SHA256 hash of x-ms-sgx-ehd) 
 
-Below claims will appear only in the attestation token generated for Intel® Xeon® Scalable processor-based server platforms. The claims will not appear if the SGX enclave is not configured with [Key Separation and Sharing Support](https://github.com/openenclave/openenclave/issues/3054). The claim definitions can be found [here](https://github.com/openenclave/openenclave/issues/3054)
+These claims will appear only in the attestation token generated for Intel® Xeon® Scalable processor-based server platforms. The claims will not appear if the SGX enclave is not configured with [Key Separation and Sharing Support](https://github.com/openenclave/openenclave/issues/3054). The claim definitions can be found [here](https://github.com/openenclave/openenclave/issues/3054):
 
 - **x-ms-sgx-config-id**
 - **x-ms-sgx-config-svn**
 - **x-ms-sgx-isv-extended-product-id**
 - **x-ms-sgx-isv-family-id**
 
-Below claims are considered deprecated but are fully supported and will continue to be included in the future. It is recommended to use the non-deprecated claim names.
+These claims are considered deprecated, but are fully supported and will continue to be included in the future. It is recommended to use the non-deprecated claim names:
 
 Deprecated claim | Recommended claim
---- | --- 
+--- | ---|
 $is-debuggable | x-ms-sgx-is-debuggable
 $product-id | x-ms-sgx-product-id
 $sgx-mrsigner | x-ms-sgx-mrsigner