edits and markdown cleanup

Author: KendalBond007

articles/healthcare-apis/azure-api-for-fhir/azure-api-fhir-access-token-validation.md

@@ -11,11 +11,11 @@ ms.author: kesheth
 ---
 # Azure API for FHIR access token validation
 
-[!INCLUDE [retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
+[!INCLUDE[retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
 
-How Azure API for FHIR validates the access token will depend on implementation and configuration. In this article, we'll walk through the validation steps, which can be helpful when troubleshooting access issues.
+How Azure API for FHIR® validates the access token will depend on implementation and configuration. In this article, we'll walk through the validation steps, which can be helpful when troubleshooting access issues.
 
-## Validate token has no issues with identity provider
+## Validate the token has no issues with identity provider
 
 The first step in the token validation is to verify that the token was issued by the correct identity provider and that it hasn't been modified. The FHIR server will be configured to use a specific identity provider known as the authority `Authority`. The FHIR server will retrieve information about the identity provider from the `/.well-known/openid-configuration` endpoint. When you use Microsoft Entra ID, the full URL is:
 
@@ -25,7 +25,7 @@ GET https://login.microsoftonline.com/<TENANT-ID>/.well-known/openid-configurati
 
 where `<TENANT-ID>` is the specific Microsoft Entra tenant (either a tenant ID or a domain name).
 
-Microsoft Entra ID will return a document like this one to the FHIR server.
+Microsoft Entra ID will return a document like the following to the FHIR server.
 
 ```json
 {
@@ -90,8 +90,9 @@ Microsoft Entra ID will return a document like this one to the FHIR server.
     "msgraph_host": "graph.microsoft.com",
     "rbac_url": "https://pas.windows.net"
 }
-``` 
-The important properties for the FHIR server are `jwks_uri`, which tells the server where to fetch the encryption keys needed to validate the token signature and `issuer`, which tells the server what will be in the issuer claim (`iss`) of tokens issued by this server. The FHIR server can use this to validate that it's receiving an authentic token.
+```
+
+The important properties for the FHIR server are `jwks_uri`, which tells the server where to fetch the encryption keys needed to validate the token signature, and `issuer`, which tells the server what will be in the issuer claim (`iss`) of tokens issued by this server. The FHIR server can use this to validate it's receiving an authentic token.
 
 ## Validate claims of the token
 
@@ -109,14 +110,14 @@ When you use the OSS Microsoft FHIR server for Azure, the server will validate:
 1. The token has the right `Audience` (`aud` claim).
 1. The token has a role in the `roles` claim, which is allowed access to the FHIR server.
 
-Consult details on how to [define roles on the FHIR server](https://github.com/microsoft/fhir-server/blob/master/docs/Roles.md).
+For details on how to [define roles on the FHIR server](https://github.com/microsoft/fhir-server/blob/master/docs/Roles.md).
 
 A FHIR server may also validate that an access token has the scopes (in token claim `scp`) to access the part of the FHIR API that a client is trying to access. Currently, Azure API for FHIR and the FHIR server for Azure don't validate token scopes.
 
 ## Next steps
-Now that you know how to walk through token validation, you can complete the tutorial to create a JavaScript application and read Fast Healthcare Interoperability Resources (FHIR&#174;) data.
+Now that you know how to validate tokens, you can complete the tutorial to create a JavaScript application and read Fast Healthcare Interoperability Resources (FHIR&#174;) data.
 
 >[!div class="nextstepaction"]
 >[Web application tutorial](tutorial-web-app-fhir-server.md)
 
-FHIR&#174; is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
+[!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

articles/healthcare-apis/azure-api-for-fhir/azure-api-fhir-resource-manager-template.md

@@ -12,13 +12,13 @@ ms.date: 09/27/2023
 
 # Quickstart: Use an ARM template to deploy Azure API for FHIR
 
-[!INCLUDE [retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
+[!INCLUDE[retirement banner](../includes/healthcare-apis-azure-api-fhir-retirement.md)]
 
-In this quickstart, you'll learn how to use an Azure Resource Manager template (ARM template) to deploy Azure API for Fast Healthcare Interoperability Resources (FHIR®). You can deploy Azure API for FHIR through the Azure portal, PowerShell, or CLI.
+In this quickstart, you learn how to use an Azure Resource Manager template (ARM template) to deploy Azure API for Fast Healthcare Interoperability Resources (FHIR®). You can deploy Azure API for FHIR through the Azure portal, PowerShell, or CLI.
 
-[!INCLUDE [About Azure Resource Manager](~/reusable-content/ce-skilling/azure/includes/resource-manager-quickstart-introduction.md)]
+[!INCLUDE[About Azure Resource Manager](~/reusable-content/ce-skilling/azure/includes/resource-manager-quickstart-introduction.md)]
 
-If your environment meets the prerequisites and you're familiar with using ARM templates, select the **Deploy to Azure** button. The template will open in the Azure portal once you sign in.
+If your environment meets the prerequisites and you're familiar with using ARM templates, select the **Deploy to Azure** button. The template opens in the Azure portal once you sign in.
 
 :::image type="content" source="~/reusable-content/ce-skilling/azure/media/template-deployments/deploy-to-azure-button.svg" alt-text="Button to deploy the Resource Manager template to Azure." border="false" link="https://portal.azure.com/#create/Microsoft.Template/uri/https%3a%2f%2fraw.githubusercontent.com%2fAzure%2fazure-quickstart-templates%2fmaster%2fquickstarts%2fmicrosoft.healthcareapis%2fazure-api-for-fhir%2fazuredeploy.json":::
 
@@ -139,7 +139,7 @@ read -p "Press [ENTER] to continue: "
 ---
 
 > [!NOTE]
-> The deployment takes a few minutes to complete. Note the names for the Azure API for FHIR service and the resource group, which you use to review the deployed resources later.
+> The deployment takes a few minutes to complete. Note the names for the Azure API for FHIR service and the resource group, for use in reviewing deployed resources.
 
 ## Review deployed resources
 
@@ -151,11 +151,11 @@ Follow these steps to see an overview of your new Azure API for FHIR service:
 
 2. In the FHIR list, select your new service. The **Overview** page for the new Azure API for FHIR service appears.
 
-3. To validate that the new FHIR API account is provisioned, select the link next to **FHIR metadata endpoint** to fetch the FHIR API capability statement. The link has a format of `https://<service-name>.azurehealthcareapis.com/metadata`. If the account is provisioned, a large JSON file is displayed.
+3. To validate that the new FHIR API account is provisioned, select the link next to **FHIR metadata endpoint** to fetch the FHIR API capability statement. The link has a format of `https://<service-name>.azurehealthcareapis.com/metadata`. If the account is provisioned, a JSON file is displayed.
 
 # [PowerShell](#tab/PowerShell)
 
-Run the following interactive code to view details about your Azure API for FHIR service. You'll have to enter the name of the new service and the resource group.
+Run the following interactive code to view details about your Azure API for FHIR service. You have to enter the name and resource group of the new service.
 
 ```azurepowershell-interactive
 $serviceName = Read-Host -Prompt "Enter the name of your Azure API for FHIR service"
@@ -172,7 +172,7 @@ Read-Host "Press [ENTER] to continue"
 
 # [CLI](#tab/CLI)
 
-Run the following interactive code to view details about your Azure API for FHIR service. You'll have to enter the name of the new service and the resource group.
+Run the following interactive code to view details about your Azure API for FHIR service. You have to enter the name of the new service and the resource group.
 
 ```azurecli-interactive
 read -p "Enter the name of your Azure API for FHIR service: " serviceName &&
@@ -189,7 +189,7 @@ read -p "Press [ENTER] to continue: "
 
 ## Clean up resources
 
-When it's no longer needed, delete the resource group, which deletes the resources in the resource group.
+When no longer needed, delete the resource group. This deletes the resources in the resource group.
 
 # [Portal](#tab/azure-portal)
 
@@ -225,7 +225,7 @@ For a step-by-step tutorial that guides you through the process of creating an A
 
 ## Next steps
 
-In this quickstart guide, you've deployed the Azure API for FHIR into your subscription. For information about how to register applications and the Azure API for FHIR configuration settings, see
+In this quickstart guide, you've deployed the Azure API for FHIR into your subscription. For information about how to register applications and the Azure API for FHIR configuration settings, see the following.
 
 
 >[!div class="nextstepaction"]
@@ -249,4 +249,4 @@ In this quickstart guide, you've deployed the Azure API for FHIR into your subsc
 >[!div class="nextstepaction"]
 >[Configure Private Link](configure-private-link.md)
 
-FHIR&#174; is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
+[!INCLUDE [FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]