Response to review comments

Author: hansenms

articles/healthcare-apis/azure-api-for-fhir-additional-settings.md

@@ -26,8 +26,8 @@ For more information on how to change the default settings, see [configure datab
 
 The Azure API for FHIR will only allow authorized users to access the FHIR API. You can configure authorized users through two different mechanisms. The primary and recommended way to configure access control is using [Azure Role Based Access Control (RBAC)](https://docs.microsoft.com/azure/role-based-access-control/), which is accessible through the **Access control (IAM)** blade. Azure RBAC only works if you want to secure data plane access using the Azure Active Directory tenant associated with your subscription. If you wish to use a different tenant, the Azure API for FHIR offers a local FHIR data plane access control mechanism. The configuration options are not as rich when using the local RBAC mechanism. For details, choose one of the following options:
 
-1. [Azure RBAC for FHIR data plane](configure-azure-rbac.md). This is the preferred option when you are using the Azure Active Directory tenant associated with your subscription.
-1. [Local FHIR data plane access control](configure-local-rbac.md). Use this option only when you need to use an external Azure Active Directory tenant for data plane access control. 
+* [Azure RBAC for FHIR data plane](configure-azure-rbac.md). This is the preferred option when you are using the Azure Active Directory tenant associated with your subscription.
+* [Local FHIR data plane access control](configure-local-rbac.md). Use this option only when you need to use an external Azure Active Directory tenant for data plane access control. 
 
 ## Enable diagnostic logging
 You may want to enable diagnostic logging as part of your setup to be able to monitor your service and have accurate reporting for compliance purposes. For details on how to set up diagnostic logging, see our [how-to-guide](enable-diagnostic-logging.md) on how to set up diagnostic logging, along with some sample queries. 

articles/healthcare-apis/configure-azure-rbac.md

@@ -1,5 +1,5 @@
 ---
-title: Configure Azure Role Based Access Control (RBAC)
+title: Configure Azure Role Based Access Control (RBAC) for Azure API for FHIR
 description: This article describes how to configure Azure RBAC for the Azure API for FHIR data plane
 author: hansenms
 ms.service: healthcare-apis
@@ -32,18 +32,18 @@ In the **Role** selection, search for one of the built-in roles for the FHIR dat
 
 You can choose between:
 
-1. FHIR Data Reader: Can read (and search) FHIR data.
-1. FHIR Data Writer: Can read, write, and soft delete FHIR data.
-1. FHIR Data Exporter: Can read and export (`$export` operator) data.
-1. FHIR Data Contributor: Can perform all data plane operations.
+* FHIR Data Reader: Can read (and search) FHIR data.
+* FHIR Data Writer: Can read, write, and soft delete FHIR data.
+* FHIR Data Exporter: Can read and export (`$export` operator) data.
+* FHIR Data Contributor: Can perform all data plane operations.
 
 If these roles are not sufficient for your need, you can also [create custom roles](https://docs.microsoft.com/azure/role-based-access-control/tutorial-custom-role-powershell).
 
 In the **Select** box, search for a user, service principal, or group that you wish to assign the role to.
 
 ## Caching behavior
 
-The Azure API for FHIR will cache decisions for up to 5 minutes. If you grant a user access to the FHIR server by adding them to the list of allowed object ids, or you remove them from the list, you should expect it to take up to five minutes for changes in permissions to propagate.
+The Azure API for FHIR will cache decisions for up to 5 minutes. If you grant a user access to the FHIR server by adding them to the list of allowed object IDs, or you remove them from the list, you should expect it to take up to five minutes for changes in permissions to propagate.
 
 ## Next steps
 

articles/healthcare-apis/configure-local-rbac.md

@@ -1,5 +1,5 @@
 ---
-title: Configure Local Role Based Access Control (RBAC)
+title: Configure local Role Based Access Control (RBAC) for Azure API for FHIR
 description: This article describes how to configure the Azure API for FHIR to use an external Azure AD tenant for data plane
 author: hansenms
 ms.service: healthcare-apis
@@ -8,7 +8,7 @@ ms.topic: reference
 ms.date: 03/15/2020
 ms.author: mihansen
 ---
-# Configure Local RBAC for FHIR 
+# Configure local RBAC for FHIR 
 
 This article explains how to configure the Azure API for FHIR to use an external, secondary Azure Active Directory tenant for managing data plane access. Use this mode only if it is not possible for you to use the Azure Active Directory tenant associated with your subscription.
 
@@ -45,17 +45,17 @@ You can configure the Azure API for FHIR to use an external or secondary Azure A
 
 In the authority box, enter a valid Azure Active Directory tenant. Once the tenant has been validated, the **Allowed object IDs** box should be activated and you can enter a list of identity object IDs. These IDs can be the identity object IDs of:
 
-1. An Azure Active Directory user.
-1. An Azure Active Directory service principal.
-1. An Azure Active directory security group.
+* An Azure Active Directory user.
+* An Azure Active Directory service principal.
+* An Azure Active directory security group.
 
 You can read the article on how to [find identity object IDs](find-identity-object-ids.md) for more details.
 
 After entering the required object IDs, click **Save** and wait for changes to be saved before trying to access the data plane using the assigned users, service principals, or groups.
 
 ## Caching behavior
 
-The Azure API for FHIR will cache decisions for up to 5 minutes. If you grant a user access to the FHIR server by adding them to the list of allowed object ids, or you remove them from the list, you should expect it to take up to five minutes for changes in permissions to propagate.
+The Azure API for FHIR will cache decisions for up to 5 minutes. If you grant a user access to the FHIR server by adding them to the list of allowed object IDs, or you remove them from the list, you should expect it to take up to five minutes for changes in permissions to propagate.
 
 ## Next steps