incorp feedback

Author: shellyhaverkamp

articles/healthcare-apis/fhir/deploy-azure-portal.md

@@ -17,7 +17,7 @@ The Azure portal provides a web interface with guided workflows, making it an ef
 
 - Verify you have an Azure subscription and permissions to create resource groups and deploy resources.
 
-- Deploy Azure Health Data Services. For steps, see [Deploy workspace in the Azure portal](../healthcare-apis-quickstart.md).
+- Deploy a workspace for Azure Health Data Services. For steps, see [Deploy workspace in the Azure portal](../healthcare-apis-quickstart.md).
 
 ## Create a new FHIR service
 
@@ -34,15 +34,17 @@ The Azure portal provides a web interface with guided workflows, making it an ef
 
      - **Integration with non-Microsoft Entra ID (optional)**: Use this option when you need to configure up to two additional identity providers other than Micrsoft Entra ID to authenticate and access FHIR resources with SMART on FHIR scopes.
 
-     - **Setting versioning policy**: The versioning policy controls the history setting for FHIR service at the system level or individual resource type level. For more information, see [FHIR versioning policy and history management](fhir-versioning-policy-and-history-management.md).
+     - **Setting versioning policy**: The versioning policy controls the history setting for FHIR service at the system level or individual resource type level. For more information, see [FHIR versioning policy and history management](fhir-versioning-policy-and-history-management.md). Choose **Next: Security**.
 
-1. Choose **Next: Security**. On the **Security settings** tab, review the fields. 
+   - On the **Security settings** tab, review the fields. 
 
-   By default, data is encrypted with Microsoft-managed keys. For additional control over encryption keys, you can supply customer-managed keys to use for encryption of data. Customer-managed keys must be stored in an Azure Key Vault. You can either create your own keys and store them in a key vault, or use the Azure Key Vault APIs to generate keys. For more information, see [Configure customer-managed keys for the FHIR service](configure-customer-managed-keys.md).
+       By default, data is encrypted with Microsoft-managed keys. For additional control over encryption keys, you can supply customer-managed keys to use for encryption of data. Customer-managed keys must be stored in an Azure Key Vault. You can either create your own keys and store them in a key vault, or use the Azure Key Vault APIs to generate keys. For more information, see [Configure customer-managed keys for the FHIR service](configure-customer-managed-keys.md). Choose **Next: Tags**. 
 
-1. Choose **Next: Tags**. On the **Tags** tab (optional), enter any tags. Tags are name and value pairs used for categorizing resources and aren't required. For more information, see [Use tags to organize your Azure resources and management hierarchy](../../azure-resource-manager/management/tag-resources.md).
+   - On the **Tags** tab (optional), enter any tags. 
+   
+     Tags are name and value pairs used for categorizing resources and aren't required. For more information, see [Use tags to organize your Azure resources and management hierarchy](../../azure-resource-manager/management/tag-resources.md).
 
-1. Choose **Review + Create** to begin the validation process. Review the details and successful validation message, and then choose **Create** to begin the deployment. 
+   - Choose **Review + Create** to begin the validation process. Wait until you receive confirmation that the deployment completed successfully. Review the confirmation screen, and then choose **Create** to begin the deployment. 
 
    The deployment process might take several minutes. When the deployment completes, you see a confirmation message.