markdown and clarity edits

KendalBond007 · KendalBond007 · commit b2e521325c8c · 2024-09-30T16:09:12.000-07:00
diff --git a/articles/healthcare-apis/azure-api-for-fhir/fhir-paas-cli-quickstart.md b/articles/healthcare-apis/azure-api-for-fhir/fhir-paas-cli-quickstart.md
@@ -1,6 +1,6 @@
 ---
 title: 'Quickstart: Deploy Azure API for FHIR using Azure CLI'
-description: In this quickstart, you'll learn how to deploy Azure API for FHIR in Azure using the Azure CLI.
+description: In this quickstart, you learn how to deploy Azure API for FHIR in Azure using the Azure CLI.
 services: healthcare-apis
 author: expekesheth
 ms.service: azure-health-data-services
@@ -13,29 +13,29 @@ ms.custom: devx-track-azurecli, mode-api
 
 # Quickstart: Deploy Azure API for FHIR using Azure CLI
 
-[!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 deploy Azure API for FHIR in Azure using the Azure CLI.
+In this quickstart, you learn how to deploy Azure API for FHIR in Azure using the Azure CLI.
 
-[!INCLUDE [quickstarts-free-trial-note](~/reusable-content/ce-skilling/azure/includes/quickstarts-free-trial-note.md)]
+[!INCLUDE[quickstarts-free-trial-note](~/reusable-content/ce-skilling/azure/includes/quickstarts-free-trial-note.md)]
 
-[!INCLUDE [azure-cli-prepare-your-environment.md](~/reusable-content/azure-cli/azure-cli-prepare-your-environment.md)]
+[!INCLUDE[azure-cli-prepare-your-environment.md](~/reusable-content/azure-cli/azure-cli-prepare-your-environment.md)]
 
 ## Add Azure Health Data Services (for example, HealthcareAPIs) extension
 
 ```azurecli-interactive
 az extension add --name healthcareapis
 ```
 
-Get a list of commands for HealthcareAPIs:
+To get a list of commands for HealthcareAPIs:
 
 ```azurecli-interactive
 az healthcareapis --help
 ```
 
 ## Create Azure Resource Group
 
-Pick a name for the resource group that will contain the Azure API for FHIR and create it:
+Pick a name for the resource group that contains the Azure API for FHIR and create it:
 
 ```azurecli-interactive
 az group create --name "myResourceGroup" --location westus2
@@ -49,23 +49,23 @@ az healthcareapis create --resource-group myResourceGroup --name nameoffhiraccou
 
 ## Fetch FHIR API capability statement
 
-Obtain a capability statement from the FHIR API with:
+Obtain a capability statement from the FHIR API with the following command:
 
 ```azurecli-interactive
 curl --url "https://nameoffhiraccount.azurehealthcareapis.com/metadata"
 ```
 
 ## Clean up resources
 
-If you're not going to continue to use this application, delete the resource group with the following steps:
+If you're not going to continue to use this application, delete the resource group with the following steps.
 
 ```azurecli-interactive
 az group delete --name "myResourceGroup"
 ```
 
 ## 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 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"]
@@ -89,4 +89,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)]
diff --git a/articles/healthcare-apis/azure-api-for-fhir/fhir-paas-portal-quickstart.md b/articles/healthcare-apis/azure-api-for-fhir/fhir-paas-portal-quickstart.md
@@ -1,6 +1,6 @@
 ---
 title: 'Quickstart: Deploy Azure API for FHIR using Azure portal'
-description: In this quickstart, you'll learn how to deploy Azure API for FHIR and configure settings using the Azure portal.
+description: In this quickstart, you learn how to deploy Azure API for FHIR and configure settings using the Azure portal.
 services: healthcare-apis
 author: expekesheth
 ms.service: azure-health-data-services
@@ -13,9 +13,9 @@ ms.custom: mode-api
 
 # Quickstart: Deploy Azure API for FHIR using Azure portal
 
-[!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 deploy Azure API for FHIR using the Azure portal.
+In this quickstart, you learn how to deploy Azure API for FHIR using the Azure portal.
 
 If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
 
@@ -39,21 +39,21 @@ Select **Create** to create a new Azure API for FHIR account:
 
 ## Enter account details
 
-Select an existing resource group or create a new one, choose a name for the account, and finally select **Review + create**:
+Select an existing resource group or create a new one. Choose a name for the account, and finally select **Review + create**:
 
 :::image type="content" source="media/quickstart-paas-portal/portal-new-healthcare-apis-details.png" alt-text="New healthcare api details":::
 
 Confirm creation and await FHIR API deployment.
 
 ## Additional settings (optional)
 
-You can also select **Next: Additional settings** to view the authentication settings. The default configuration for the Azure API for FHIR is to [use Azure RBAC for assigning data plane roles](configure-azure-rbac.md). When configured in this mode, the "Authority" for the FHIR service will be set to the Microsoft Entra tenant of the subscription:
+You can also select **Next: Additional settings** to view the authentication settings. The default configuration for the Azure API for FHIR is to [use Azure role-based access control (RBAC) for assigning data plane roles](configure-azure-rbac.md). When configured in this mode, the "Authority" for the FHIR service is set to the Microsoft Entra tenant of the subscription.
 
 :::image type="content" source="media/rbac/confirm-azure-rbac-mode-create.png" alt-text="Default Authentication settings":::
 
 Notice that the box for entering allowed object IDs is grayed out, since we use Azure RBAC for configuring role assignments in this case.
 
-If you wish to configure the FHIR service to use an external or secondary Microsoft Entra tenant, you can change the Authority and enter object IDs for user and groups that should be allowed access to the server. For more information, see the [local RBAC configuration](configure-local-rbac.md) guide.
+If you wish to configure the FHIR service to use an external or secondary Microsoft Entra tenant, you can change the Authority and enter object IDs for users and groups that should be allowed access to the server. For more information, see the [local RBAC configuration](configure-local-rbac.md) guide.
 
 ## Fetch FHIR API capability statement
 
@@ -65,7 +65,7 @@ When no longer needed, you can delete the resource group, Azure API for FHIR, an
 
 ## 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 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
 
 
 >[!div class="nextstepaction"]
@@ -89,4 +89,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)]
diff --git a/articles/healthcare-apis/azure-api-for-fhir/fhir-paas-powershell-quickstart.md b/articles/healthcare-apis/azure-api-for-fhir/fhir-paas-powershell-quickstart.md
@@ -1,6 +1,6 @@
 ---
 title: 'Quickstart: Deploy Azure API for FHIR using PowerShell'
-description: In this quickstart, you'll learn how to deploy Azure API for FHIR using PowerShell.
+description: In this quickstart, you learn how to deploy Azure API for FHIR using PowerShell.
 services: healthcare-apis
 author: expekesheth
 ms.service: azure-health-data-services
@@ -13,19 +13,19 @@ ms.custom: devx-track-azurepowershell
 
 # Quickstart: Deploy Azure API for FHIR using PowerShell
 
-[!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 deploy Azure API for FHIR using PowerShell.
+In this quickstart, you learn how to deploy Azure API for FHIR using PowerShell.
 
 If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
 
-[!INCLUDE [cloud-shell-try-it.md](~/reusable-content/ce-skilling/azure/includes/cloud-shell-try-it.md)]
+[!INCLUDE[cloud-shell-try-it.md](~/reusable-content/ce-skilling/azure/includes/cloud-shell-try-it.md)]
 
-[!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
+[!INCLUDE[updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
 
 ## Register the Azure API for FHIR resource provider
 
-If the `Microsoft.HealthcareApis` resource provider isn't already registered for your subscription, you can register it with:
+If the `Microsoft.HealthcareApis` resource provider isn't already registered for your subscription, you can register it with the following command.
 
 ```azurepowershell-interactive
 Register-AzResourceProvider -ProviderNamespace Microsoft.HealthcareApis
@@ -44,12 +44,12 @@ New-AzHealthcareApisService -Name nameoffhirservice -ResourceGroupName myResourc
 ```
 
 > [!NOTE]
-> Depending on the version of the `Az` PowerShell module you have installed, the provisioned FHIR server may be configured to use [local RBAC](configure-local-rbac.md) and have the currently signed in PowerShell user set in the list of allowed identity object IDs for the deployed FHIR service. Going forward, we recommend that you [use Azure RBAC](configure-azure-rbac.md) for assigning data plane roles and you may need to delete this users object ID after deployment to enable Azure RBAC mode.
+> Depending on the version of the `Az` PowerShell module you have installed, the provisioned FHIR server may be configured to use [local role-based access control (RBAC)](configure-local-rbac.md) and have the currently signed in PowerShell user in the list of allowed identity object IDs for the deployed FHIR service. We recommend you [use Azure RBAC](configure-azure-rbac.md) for assigning data plane roles. You may need to delete this user's object ID after deployment to enable Azure RBAC mode.
 
 
 ## Fetch capability statement
 
-You'll be able to validate that the Azure API for FHIR account is running by fetching a FHIR capability statement:
+You can validate that the Azure API for FHIR account is running by fetching a FHIR capability statement with the following commands.
 
 ```azurepowershell-interactive
 $metadata = Invoke-WebRequest -Uri "https://nameoffhirservice.azurehealthcareapis.com/metadata"
@@ -58,15 +58,15 @@ $metadata.RawContent
 
 ## Clean up resources
 
-If you're not going to continue to use this application, delete the resource group with the following steps:
+If you're not going to continue using this application, delete the resource group with the following steps.
 
 ```azurepowershell-interactive
 Remove-AzResourceGroup -Name myResourceGroupName
 ```
 
 ## Next steps
 
-In this quickstart guide, you've deployed the Azure API for FHIR into your subscription. For more information about the settings in Azure API for FHIR and to start using Azure API for FHIR, see
+In this quickstart guide, you deployed the Azure API for FHIR into your subscription. For more information about the settings in Azure API for FHIR and to start using Azure API for FHIR, see
 
 >[!div class="nextstepaction"]
 >[Additional settings in Azure API for FHIR](azure-api-for-fhir-additional-settings.md)
@@ -92,4 +92,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)]
diff --git a/articles/healthcare-apis/azure-api-for-fhir/fhir-rest-api-capabilities.md b/articles/healthcare-apis/azure-api-for-fhir/fhir-rest-api-capabilities.md
