correcting de-ident caps

KendalBond007 · KendalBond007 · commit 11ddb9287147 · 2024-08-20T09:37:03.000-07:00
diff --git a/articles/healthcare-apis/deidentification/manage-access-rbac.md b/articles/healthcare-apis/deidentification/manage-access-rbac.md
@@ -9,21 +9,21 @@ ms.topic: how-to
 ms.date: 07/16/2024
 ---
 
-# Use Azure role-based access control with the De-identification service (preview)
+# Use Azure role-based access control with the de-identification service (preview)
 
-Microsoft Entra ID authorizes access rights to secured resources through Azure role-based access control (RBAC). The De-identification service (preview) defines a set of built-in roles that encompass common sets of permissions used to access de-identification functionality.
+Microsoft Entra ID authorizes access rights to secured resources through Azure role-based access control (RBAC). The de-identification service (preview) defines a set of built-in roles that encompass common sets of permissions used to access de-identification functionality.
 
 Microsoft Entra ID uses the concept of a security principal, which can be a user, a group, an application service principal, or a [managed identity for Azure resources](/entra/identity/managed-identities-azure-resources/overview).
 
 When an Azure role is assigned to a Microsoft Entra ID security principal over a specific scope, Azure grants access to that scope for that security principal. For more information about scopes, see [Understand scope for Azure RBAC](/azure/role-based-access-control/scope-overview).
 
 ## Prerequisites
 
-- A De-identification service (preview) in your Azure subscription. If you don't have a de-identification service, follow the steps in [Quickstart: Deploy the de-identification service](quickstart.md).
+- A de-identification service (preview) in your Azure subscription. If you don't have a de-identification service, follow the steps in [Quickstart: Deploy the de-identification service](quickstart.md).
 
 ## Available built-in roles
 
-The De-identification service (preview) has the following built-in roles available:
+The de-identification service (preview) has the following built-in roles available:
 
 |Role |Description |
 |-----|------------|
@@ -34,7 +34,7 @@ The De-identification service (preview) has the following built-in roles availab
 
 ## Assign a built-in role
 
-Keep in mind the following points about Azure role assignments with the De-identification service (preview):
+Keep in mind the following points about Azure role assignments with the de-identification service (preview):
 
 - When you create a de-identification service, you aren't automatically assigned permissions to access data via Microsoft Entra ID. You need to explicitly assign yourself an applicable Azure role. You can assign it at the level of your subscription, resource group, or de-identification service.
 - When roles are assigned, it can take up to 10 minutes for changes to take effect.
@@ -45,15 +45,15 @@ You can use different tools to assign built-in roles. Select the tab that applie
 
 # [Azure portal](#tab/azure-portal)
 
-To use the De-identification service (preview), with Microsoft Entra ID credentials, a security principal must be assigned one of the built-in roles. To learn how to assign these roles to a security principal, follow the steps in [Assign Azure roles using the Azure portal](/azure/role-based-access-control/role-assignments-portal).
+To use the de-identification service (preview), with Microsoft Entra ID credentials, a security principal must be assigned one of the built-in roles. To learn how to assign these roles to a security principal, follow the steps in [Assign Azure roles using the Azure portal](/azure/role-based-access-control/role-assignments-portal).
 
 # [Azure PowerShell](#tab/azure-powershell)
 
 To assign an Azure role to a security principal with PowerShell, call the [New-AzRoleAssignment](/powershell/module/az.resources/new-azroleassignment) command. In order to run the command, you must have a role that includes **Microsoft.Authorization/roleAssignments/write** permissions assigned to you at the corresponding scope or higher.
 
 The format of the command can differ based on the scope of the assignment, but `ObjectId` and `RoleDefinitionName` are required parameters. While the `Scope` parameter is optional, you should set it to retain the principle of least privilege. By limiting roles and scopes, you limit the resources that are at risk if the security principal is ever compromised.
 
-The scope for a De-identification service (preview) is in the form `/subscriptions/<Subscription ID>/resourceGroups/<Resource Group Name>/providers/Microsoft.HealthDataAIServices/deidServices/<Deidentification Service Name>`
+The scope for a de-identification service (preview) is in the form `/subscriptions/<Subscription ID>/resourceGroups/<Resource Group Name>/providers/Microsoft.HealthDataAIServices/deidServices/<Deidentification Service Name>`
 
 The example assigns the **DeID Data Owner** built-in role to a user, scoped to a specific de-identification service. Make sure to replace the placeholder values 
 in angle brackets `<>` with your own values:
@@ -88,7 +88,7 @@ To assign an Azure role to a security principal with Azure CLI, use the [az role
 
 The format of the command can differ based on the type of security principal, but `role` and `scope` are required parameters.
 
-The scope for a De-identification service (preview) is in the form `/subscriptions/<Subscription ID>/resourceGroups/<Resource Group Name>/providers/Microsoft.HealthDataAIServices/deidServices/<Deidentification Service Name>`
+The scope for a de-identification service (preview) is in the form `/subscriptions/<Subscription ID>/resourceGroups/<Resource Group Name>/providers/Microsoft.HealthDataAIServices/deidServices/<Deidentification Service Name>`
 
 The following example assigns the **DeID Data Owner** built-in role to a user, scoped to a specific de-identification service. Make sure to replace the placeholder values in angle brackets `<>` with your own values:
 
diff --git a/articles/healthcare-apis/deidentification/managed-identities.md b/articles/healthcare-apis/deidentification/managed-identities.md
@@ -9,22 +9,22 @@ ms.topic: how-to
 ms.date: 07/17/2024
 ---
 
-# Use managed identities with the De-identification service (preview)
+# Use managed identities with the de-identification service (preview)
 
 Managed identities provide Azure services with a secure, automatically managed identity in Microsoft Entra ID. Using managed identities eliminates the need for developers to manage credentials by providing an identity. There are two types of managed identities: system-assigned and user-assigned. The de-identification service supports both.
 
-Managed identities can be used to grant the De-identification service (preview) access to your storage account for batch processing. In this article, you learn how to assign a managed identity to your de-identification service.
+Managed identities can be used to grant the de-identification service (preview) access to your storage account for batch processing. In this article, you learn how to assign a managed identity to your de-identification service.
 
 ## Prerequisites
 
 - Understand the differences between **system-assigned** and **user-assigned** managed identities, described in [What are managed identities for Azure resources?](/entra/identity/managed-identities-azure-resources/overview)
-- A De-identification service (preview) in your Azure subscription. If you don't have a de-identification service, follow the steps in [Quickstart: Deploy the de-identification service](quickstart.md).
+- A de-identification service (preview) in your Azure subscription. If you don't have a de-identification service, follow the steps in [Quickstart: Deploy the de-identification service](quickstart.md).
 
-## Create an instance of the De-identification service (preview) in Azure Health Data Services with a system-assigned managed identity
+## Create an instance of the de-identification service (preview) in Azure Health Data Services with a system-assigned managed identity
 
 # [Azure portal](#tab/portal)
 
-1. Access the De-identification service (preview) settings in the Azure portal under the **Security** group in the left navigation pane.
+1. Access the de-identification service (preview) settings in the Azure portal under the **Security** group in the left navigation pane.
 1. Select **Identity**.
 1. Within the **System assigned** tab, switch **Status** to **On** and choose **Save**.
 
@@ -46,7 +46,7 @@ the resource definition:
 # [Azure portal](#tab/portal)
 
 1. Create a user-assigned managed identity resource according to [these instructions](/entra/identity/managed-identities-azure-resources/how-manage-user-assigned-managed-identities).
-1. In the navigation pane of your De-identification service (preview), scroll to the **Security** group.
+1. In the navigation pane of your de-identification service (preview), scroll to the **Security** group.
 1. Select **Identity**.
 1. Select the **User assigned** tab, and then choose **Add**.
 1. Search for the identity you created, select it, and then choose **Add**.
@@ -69,16 +69,16 @@ the resource definition, replacing **resource-id** with the Azure Resource Manag
 
 ## Supported scenarios using managed identities
 
-Managed identities assigned to the De-identification service (preview) can be used to allow access to Azure Blob Storage for batch de-identification jobs. The service acquires a token as the managed identity to access Blob Storage, and de-identify blobs that match a specified pattern. For more information, including how to grant access to your managed identity, see [Quickstart: Azure Health De-identification client library for .NET](quickstart-sdk-net.md).
+Managed identities assigned to the de-identification service (preview) can be used to allow access to Azure Blob Storage for batch de-identification jobs. The service acquires a token as the managed identity to access Blob Storage, and de-identify blobs that match a specified pattern. For more information, including how to grant access to your managed identity, see [Quickstart: Azure Health De-identification client library for .NET](quickstart-sdk-net.md).
 
 ## Clean-up steps
 
 When you remove a system-assigned identity, you delete it from Microsoft Entra ID. System-assigned identities are also automatically removed from Microsoft Entra ID
-when you delete the De-identification service (preview), described as follows.
+when you delete the de-identification service (preview), described as follows.
 
 # [Azure portal](#tab/portal)
 
-1. In the navigation pane of your De-identification service (preview), scroll down to the **Security** group.
+1. In the navigation pane of your de-identification service (preview), scroll down to the **Security** group.
 1. Select **Identity**, then follow the steps based on the identity type:
    - **System-assigned identity**: Within the **System assigned** tab, switch **Status** to **Off**, and then choose **Save**.
    - **User-assigned identity**: Select the **User assigned** tab, select the checkbox for the identity, and select **Remove**. Select **Yes** to confirm.
diff --git a/articles/healthcare-apis/deidentification/overview.md b/articles/healthcare-apis/deidentification/overview.md
@@ -9,13 +9,13 @@ ms.date: 7/17/2024
 ms.author: kimiamavon
 ---
 
-# What is the De-identification service (preview)?
+# What is the de-identification service (preview)?
 
-The De-identification service (preview) in Azure Health Data Services enables healthcare organizations to anonymize clinical data so that the resulting data retains its clinical relevance and distribution while also adhering to the Health Insurance Portability and Accountability Act of 1996 (HIPAA) Privacy Rule. The service uses state-of-the-art machine learning models to automatically extract, redact, or surrogate 28 entities - including the HIPAA 18 Protected Health Information (PHI) identifiers – from unstructured text such as clinical notes, transcripts, messages, or clinical trial studies.
+The de-identification service (preview) in Azure Health Data Services enables healthcare organizations to anonymize clinical data so that the resulting data retains its clinical relevance and distribution while also adhering to the Health Insurance Portability and Accountability Act of 1996 (HIPAA) Privacy Rule. The service uses state-of-the-art machine learning models to automatically extract, redact, or surrogate 28 entities - including the HIPAA 18 Protected Health Information (PHI) identifiers – from unstructured text such as clinical notes, transcripts, messages, or clinical trial studies.
 
 ## Use de-identified data in research, analytics, and machine learning
 
-The De-identification service (preview) unlocks data that was previously difficult to de-identify so organizations can conduct research and derive insights from analytics. The De-identification service supports three operations: **tag**, **redact**, or **surrogate PHI**. The de-identification service offers many benefits, including:
+The de-identification service (preview) unlocks data that was previously difficult to de-identify so organizations can conduct research and derive insights from analytics. The de-identification service supports three operations: **tag**, **redact**, or **surrogate PHI**. The de-identification service offers many benefits, including:
 
 - **Surrogation**: Surrogation, or replacement, is a best practice for PHI protection. The service can replace PHI elements with plausible replacement values, resulting in data that is most representative of the source data. Surrogation strengthens privacy protections as any false-negative PHI values are hidden within a document.
 
@@ -25,7 +25,7 @@ The De-identification service (preview) unlocks data that was previously difficu
 
 ## De-identify clinical data securely and efficiently
 
-The De-identification service (preview) offers many benefits, including:
+The de-identification service (preview) offers many benefits, including:
 
 - **PHI compliance**: The de-identification service is designed for protected health information (PHI). The service uses machine learning to identify PHI entities, including HIPAA’s 18 identifiers, using the “TAG” operation. The redaction and surrogation operations replace these identified PHI values with a tag of the entity type or a surrogate, or pseudonym. The service also meets all regional compliance requirements including HIPAA, GDPR, and the California Consumer Privacy Act (CCPA).
 
@@ -35,14 +35,14 @@ The De-identification service (preview) offers many benefits, including:
 
 ## Synchronous or asynchronous endpoints
 
-The De-identification service (preview) offers two ways to interact with the REST API or Client library (Azure SDK).
+The de-identification service (preview) offers two ways to interact with the REST API or Client library (Azure SDK).
 
 - Directly submit raw unstructured text for analysis. The API output is returned in your application.
 - Submit a job to asynchronously endpoint process files in bulk from Azure Blob Storage using tag, redact, or surrogation with consistency within a job.
 
 ## Input requirements and service limits
 
-The De-identification service (preview) is designed to receive unstructured text. To de-identify data stored in the FHIR&reg; service, see [Export deidentified data](/azure/healthcare-apis/fhir/deidentified-export).
+The de-identification service (preview) is designed to receive unstructured text. To de-identify data stored in the FHIR&reg; service, see [Export deidentified data](/azure/healthcare-apis/fhir/deidentified-export).
 
 The following service limits are applicable during preview:
 - Requests can't exceed 50 KB.
@@ -60,7 +60,7 @@ When you choose to store documents in Azure Blob Storage, you are charged based
 
 ## Responsible use of AI
 
-An AI system includes the technology, the people who use it, the people affected by it, and the environment where you deploy it. Read the transparency note for the De-identification service (preview) to learn about responsible AI use and deployment in your systems.
+An AI system includes the technology, the people who use it, the people affected by it, and the environment where you deploy it. Read the transparency note for the de-identification service (preview) to learn about responsible AI use and deployment in your systems.
 
 ## Related content
 
diff --git a/articles/healthcare-apis/deidentification/quickstart-sdk-net.md b/articles/healthcare-apis/deidentification/quickstart-sdk-net.md
@@ -1,5 +1,5 @@
 ---
-title: "Quickstart: Azure Health De-identification client library for .NET"
+title: "Quickstart: Azure Health de-identification client library for .NET"
 description: A quickstart guide to de-identify health data with the .NET client library
 author: GrahamMThomas
 ms.author: gthomas
@@ -25,7 +25,7 @@ Get started with the Azure Health De-identification client library for .NET to d
 
 ### Create a Deidentification service (preview)
 
-A De-identification service (preview) provides you with an endpoint URL. This endpoint url can be utilized as a Rest API or with an SDK.
+A de-identification service (preview) provides you with an endpoint URL. This endpoint url can be utilized as a Rest API or with an SDK.
 
 1. Install [Azure CLI](/cli/azure/install-azure-cli)
 2. Create a de-identification service resource
@@ -47,9 +47,9 @@ A De-identification service (preview) provides you with an endpoint URL. This en
     az storage account create --name $STORAGE_ACCOUNT_NAME --resource-group $RESOURCE_GROUP_NAME --location $REGION
     ```
 
-### Authorize Deidentification service (preview) on Azure Storage Account
+### Authorize deidentification service (preview) on Storage Account
 
--  Give the De-identification service (preview) access to your storage account
+-  Give the de-identification service (preview) access to your storage account
    
    ```bash
     STORAGE_ACCOUNT_ID=$(az storage account show --name $STORAGE_ACCOUNT_NAME --resource-group $RESOURCE_GROUP_NAME --query id --output tsv)
@@ -90,7 +90,7 @@ The client library is available through NuGet, as the `Azure.Health.Deidentifica
 
 ### Create a deidentification client
 
-Before you can create the client, you need to find your **De-identification service (preview) endpoint URL**.
+Before you can create the client, you need to find your **de-identification service (preview) endpoint URL**.
 
 You can find the endpoint URL with the Azure CLI:
 
@@ -198,9 +198,9 @@ az role assignment delete --assignee $DEID_SERVICE_PRINCIPAL_ID --role "Storage
 
 ### Unable to access source or target storage
 
-Ensure the permissions are given, and the Managed Identity for the De-identification service (preview) is set up properly.
+Ensure the permissions are given, and the Managed Identity for the de-identification service (preview) is set up properly.
 
-See [Authorize Deidentification Service on Storage Account](#authorize-deidentification-service-preview-on-azure-storage-account)
+See [Authorize deidentification service on Storage Account](#authorize-deidentification-service-preview-on-storage-account)
 
 ### Job failed with status PartialFailed
 
@@ -212,7 +212,7 @@ See [Sample](https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/healthdata
 ## Next steps
 
 In this quickstart, you learned:
-- How to create a De-identification service (preview) and assign a role on a storage account.
+- How to create a de-identification service (preview) and assign a role on a storage account.
 - How to create a deidentification client
 - How to de-identify strings and create jobs on documents within a storage account.
 
diff --git a/articles/healthcare-apis/deidentification/quickstart.md b/articles/healthcare-apis/deidentification/quickstart.md
