markdown cleanup, edits for clarity

Author: KendalBond007

articles/healthcare-apis/fhir/configure-identity-providers.md

@@ -13,7 +13,7 @@ ms.author: namalu
 
 # Configure multiple service identity providers
 
-In addition to [Microsoft Entra ID](/entra/fundamentals/whatis), you can configure up to two additional identity providers for a FHIR service, whether the service already exists or is newly created. 
+In addition to [Microsoft Entra ID](/entra/fundamentals/whatis), you can configure up to two additional identity providers for a FHIR® service, whether the service already exists or is newly created. 
 
 ## Identity providers prerequisite
 Identity providers must support OpenID Connect (OIDC), and must be able to issue JSON Web Tokens (JWT) with a `fhirUser` claim, a `azp` or `appid` claim, and an `scp` claim with [SMART on FHIR v1 Scopes](https://www.hl7.org/fhir/smart-app-launch/1.0.0/scopes-and-launch-context/index.html#scopes-for-requesting-clinical-data).
@@ -58,7 +58,7 @@ Add the `smartIdentityProviders` element to the FHIR service `authenticationConf
 
 #### Configure the `smartIdentityProviders` array
 
-If you don't need any identity providers besides Microsoft Entra ID, set the `smartIdentityProviders` array to null, or omit it from the provisioning request. Otherwise, include at least one valid identity provider configuration object in the array. You can configure up to two additional identity providers.
+If you don't need any identity providers beside Microsoft Entra ID, set the `smartIdentityProviders` array to null, or omit it from the provisioning request. Otherwise, include at least one valid identity provider configuration object in the array. You can configure up to two additional identity providers.
 
 #### Specify the `authority`
 
@@ -74,19 +74,19 @@ https://yourIdentityProvider.com/authority/v2.0/.well-known/openid-configuration
 
 #### Configure the `applications` array
 
-You must include at least one application configuration and can add upto 25 applications in the `applications` array. Each application configuration has values that validate access token claims and an array that defines the permissions for the application to access FHIR resources.
+You must include at least one application configuration and can add up to 25 applications in the `applications` array. Each application configuration has values that validate access token claims, and an array that defines the permissions for the application to access FHIR resources.
 
 #### Identify the application with the `clientId` string
 
-The identity provider defines the application with a unique identifier called the `clientId` string (or application ID). The FHIR service validates the access token by checking the `authorized party` (azp) or `application id` (appid) claim against the `clientId` string. The FHIR service rejects requests with a `401 Unauthorized` error code if the `clientId` string and the token claim don't match exactly.
+The identity provider defines the application with a unique identifier called the `clientId` string (or application ID). The FHIR service validates the access token by checking the `authorized party` (azp) or `application id` (appid) claim against the `clientId` string. If the `clientId` string and the token claim don't match exactly, the FHIR service rejects the request with a `401 Unauthorized` error code.
 
 #### Validate the access token with the `audience` string
 
-The `aud` claim in an access token identifies the intended recipient of the token. The `audience` string is the unique identifier for the recipient. The FHIR service validates the access token by checking the `audience` string against the `aud` claim. The FHIR service rejects requests with a `401 Unauthorized` error code if the `audience` string and the `aud` claim don't match exactly.
+The `aud` claim in an access token identifies the intended recipient of the token. The `audience` string is the unique identifier for the recipient. The FHIR service validates the access token by checking the `audience` string against the `aud` claim. If the `audience` string and the `aud` claim don't match exactly, the FHIR service rejects requests with a `401 Unauthorized` error code.
 
 #### Specify the permissions with the `allowedDataActions` array
 
-Include at least one permission string in the `allowedDataActions` array. You can include any valid permission strings, but avoid duplicates.
+Include at least one permission string in the `allowedDataActions` array. You can include any valid permission strings. Avoid duplicates.
 
 | **Valid permission string** | **Description** |
 |---|---|

articles/healthcare-apis/fhir/configure-import-data.md

@@ -11,10 +11,10 @@ ms.author: kesheth
 
 # Configure FHIR import settings
 
-This article walks you through the steps to configure settings on the FHIR service for `import` operations. To configure settings, you need to:
+This article walks you through the steps to configure settings on the FHIR® service for `import` operations. To configure settings, you need to:
 
 1. Enable a managed identity on the FHIR service.
-1. Create an Azure storage account or use an existing storage account, and then grant permissions to the FHIR service to access it.
+1. Create an Azure storage account or use an existing storage account, and grant permissions for the FHIR service to access it.
 1. Set the import configuration of the FHIR service.
 1. Use one of the options to securely import FHIR data into the FHIR service from an Azure Data Lake Storage Gen2 account.
 
@@ -35,7 +35,7 @@ After you enable the managed identity, a system-assigned GUID value appears.
 
 ## Step 2: Assign permissions to the FHIR service
 
-Use the following steps to assign permissions to access the storage account:
+Use the following steps to assign permissions to access the storage account.
 
 1. In the storage account, browse to **Access Control (IAM)**.
 2. Select **Add role assignment**. If the option for adding a role assignment is unavailable, ask your Azure administrator to assign you permission to perform this step.
@@ -53,14 +53,13 @@ Now you're ready to select the storage account for import.
 > [!NOTE]
 > If you haven't assigned storage access permissions to the FHIR service, the `import` operation will fail.
 
-For this step, you need to get the request URL and JSON body:
+For this step, you need to get the request URL and JSON body.
 
 1. In the Azure portal, browse to your FHIR service.
 2. Select **Overview**.
 3. Select **JSON View**.
 4. Select the API version as **2022-06-01** or later.
 
-
 To specify the Azure storage account in JSON view which is in **READ** mode, you need to use the [REST API](/rest/api/healthcareapis/services/create-or-update) to update the FHIR service.
 
 [![Screenshot of selections for opening the JSON view.](media/bulk-import/fhir-json-view.png)](media/bulk-import/fhir-json-view.png#lightbox)
@@ -69,7 +68,7 @@ The following steps walk you through setting configurations for initial and incr
 
 ### Set the import configuration for initial import mode
 
-Make the following changes to JSON:
+Make the following changes to JSON.
 
 1. In `importConfiguration`, set `enabled` to `true`.
 2. Update `integrationDataStore` with the target storage account name.
@@ -82,7 +81,7 @@ You're now ready to perform initial-mode import by using `import`.
 
 ### Set the import configuration for incremental import mode
 
-Make the following changes to JSON:
+Make the following changes to JSON.
 
 1. In `importConfiguration`, set `enabled` to `true`.
 2. Update `integrationDataStore` with the target storage account name.
@@ -105,7 +104,7 @@ To securely import FHIR data into the FHIR service from an Azure Data Lake Stora
 
 ### Enable the FHIR service as a trusted Microsoft service
 
-1. In the Azure portal, go to your Data Lake Storage Gen2 account in the Azure portal.
+1. In the Azure portal, go to your Data Lake Storage Gen2 account.
 
 1. On the left menu, select **Networking**.
 
@@ -153,9 +152,9 @@ You're now ready to securely import FHIR data from the storage account. The stor
 
 ## Next steps
 
-In this article, you learned how the FHIR service supports the `import` operation and how you can import data into the FHIR service from a storage account. You also learned about the steps for configuring import settings in the FHIR service. For more information about converting data to FHIR, exporting settings to set up a storage account, and moving data to Azure Synapse Analytics, see:
+In this article, you learned how the FHIR service supports the `import` operation, and how you can import data into the FHIR service from a storage account. You also learned about the steps for configuring import settings in the FHIR service. For more information about converting data to FHIR, exporting settings to set up a storage account, and moving data to Azure Synapse Analytics, see:
 
 >[!div class="nextstepaction"]
 >[Import FHIR data](import-data.md)
 
-FHIR® 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)]