@@ -106,7 +106,7 @@ Start configuring secure communications by navigating to the **Networking** tab
 
 To ensure that the Document Intelligence resource can access the training dataset, you need to add a role assignment for your [managed identity](#setup-managed-identity-for-document-intelligence).
 
-1. Staying on the storage account window in the Azure portal, navigate to the **Access Control (IAM)** tab in the left navigation bar.
+1. Staying on the storage account window in the Azure portal, navigate to the **Access Control (IAM)** tab in the left pane.
 
 1. Select the **Add role assignment** button.
 
@@ -157,7 +157,7 @@ Next, configure the virtual network to ensure only resources within the virtual
 
 1. In the Azure portal, navigate to your Document Intelligence resource.
 
-1. Select the **Networking** tab from the left navigation bar.
+1. Select the **Networking** tab from the left pane.
 
 1. Enable the **Selected Networking and Private Endpoints** option from the **Firewalls and virtual networks** tab and select save.
 
@@ -209,7 +209,7 @@ Well done! Your Document Intelligence resource now is only accessible from the v
 
 Navigate to your **storage account** on the Azure portal.
 
-1. Select the **Networking** tab from the left navigation menu.
+1. Select the **Networking** tab from the left pane.
 
 1. Select the **Private endpoint connections** tab.
 

@@ -23,7 +23,7 @@ Azure AI Document Intelligence is an Azure AI service that lets you build automa
 
 In this article you can learn how to download, install, and run Document Intelligence containers. Containers enable you to run the Document Intelligence service in your own environment. Containers are great for specific security and data governance requirements.
 
-* **Layout** model is supported by Document Intelligence v3.1 containers.
+* **Layout** model is supported by Document Intelligence v4.0 containers.
 
 * **Read**, **Layout**,  **ID Document**,  **Receipt**, and **Invoice**  models are supported by Document Intelligence v3.1 containers.
 

@@ -59,7 +59,7 @@ Let's get started:
 
 1. Copy the key and endpoint values from your Document Intelligence resource paste them in a convenient location, such as *Microsoft Notepad*. You need the key and endpoint values to connect your application to the Document Intelligence API.
 
-1. If your overview page doesn't have the keys and endpoint visible, you can select the **Keys and Endpoint** button, on the left navigation bar, and retrieve them there.
+1. If your overview page doesn't have the keys and endpoint visible, you can select the **Keys and Endpoint** button, on the left pane, and retrieve them there.
 
     :::image border="true" type="content" source="../media/containers/keys-and-endpoint.png" alt-text="Still photo showing how to access resource key and endpoint URL.":::
 

@@ -39,7 +39,7 @@ We start by looking at the page processing data for a given time period:
 
 We can now take a deeper dive to see each model's analyzed pages:
 
-1. Under the **Monitoring** section, select **Metrics** from the left navigation menu.
+1. Under the **Monitoring** section, select **Metrics** from the left pane.
 
    :::image type="content" source="../media/azure-portal-monitoring-metrics.png" alt-text="Screenshot of the monitoring menu in the Azure portal.":::
 

@@ -30,7 +30,7 @@ ms.custom: devx-track-csharp
 - The key and endpoint from the resource you create to connect your application to the Azure Document Intelligence service.
 
   1. After your resource deploys, select **Go to resource**.
-  1. In the left navigation menu, select **Keys and Endpoint**.
+  1. In the left pane, select **Keys and Endpoint**.
   1. Copy one of the keys and the **Endpoint** for use later in this article.
 
   :::image type="content" source="../../../media/containers/keys-and-endpoint.png" alt-text="Screenshot of keys and endpoint location in the Azure portal.":::
@@ -74,7 +74,7 @@ From the project directory, open the *Program.cs* file in an editor or IDE. Add
 In the application's `Program` class, create variables for your resource's key and endpoint.
 
 > [!IMPORTANT]
-> Go to the Azure portal. If the Document Intelligence resource you created in the Prerequisites section deployed successfully, select the **Go to Resource** button under **Next Steps**. In the left navigation menu, under **Resource Management**, select **Keys and Endpoint**.
+> Go to the Azure portal. If the Document Intelligence resource you created in the Prerequisites section deployed successfully, select the **Go to Resource** button under **Next Steps**. In the left pane, under **Resource Management**, select **Keys and Endpoint**.
 >
 > Remember to remove the key from your code when you're done. Never post it publicly. For production, use secure methods to store and access your credentials. For more information, see [Azure AI services security](../../../../../ai-services/security-features.md).
 

@@ -29,7 +29,7 @@ ms.author: lajanuar
 - The key and endpoint from the resource you create to connect your application to the Azure Document Intelligence service.
 
   1. After your resource deploys, select **Go to resource**.
-  1. In the left navigation menu, select **Keys and Endpoint**.
+  1. In the left pane, select **Keys and Endpoint**.
   1. Copy one of the keys and the **Endpoint** for use later in this article.
 
   :::image type="content" source="../../../media/containers/keys-and-endpoint.png" alt-text="Screenshot of keys and endpoint location in the Azure portal.":::

@@ -30,7 +30,7 @@ ms.custom: devx-track-js
 - The key and endpoint from the resource you create to connect your application to the Azure Document Intelligence service.
 
   1. After your resource deploys, select **Go to resource**.
-  1. In the left navigation menu, select **Keys and Endpoint**.
+  1. In the left pane, select **Keys and Endpoint**.
   1. Copy one of the keys and the **Endpoint** for use later in this article.
 
   :::image type="content" source="../../../media/containers/keys-and-endpoint.png" alt-text="Screenshot of keys and endpoint location in the Azure portal.":::

@@ -27,7 +27,7 @@ ms.custom: devx-track-python
 - A Document Intelligence resource. <a href="https://portal.azure.com/#create/Microsoft.CognitiveServicesFormRecognizer"  title="Create a Document Intelligence resource."  target="_blank">Create a Document Intelligence resource </a> in the Azure portal. You can use the free pricing tier (`F0`) to try the service, and upgrade later to a paid tier for production.
 
   1. After your resource deploys, select **Go to resource**.
-  1. In the left navigation menu, select **Keys and Endpoint**.
+  1. In the left pane, select **Keys and Endpoint**.
   1. Copy one of the keys and the **Endpoint** for use later in this article.
 
   :::image type="content" source="../../../media/containers/keys-and-endpoint.png" alt-text="Screenshot of keys and endpoint location in the Azure portal.":::

@@ -39,7 +39,7 @@ ms.author: lajanuar
 - The key and endpoint from the resource you create to connect your application to the Azure Document Intelligence service.
 
   1. After your resource deploys, select **Go to resource**.
-  1. In the left navigation menu, select **Keys and Endpoint**.
+  1. In the left pane, select **Keys and Endpoint**.
   1. Copy one of the keys and the **Endpoint** for use later in this article.
 
   :::image type="content" source="../../../media/containers/keys-and-endpoint.png" alt-text="Screenshot of keys and endpoint location in the Azure portal.":::

@@ -33,7 +33,7 @@ monikerRange: 'doc-intel-3.1.0 || doc-intel-3.0.0'
 - The key and endpoint from the resource you create to connect your application to the Azure Document Intelligence service.
 
   1. After your resource deploys, select **Go to resource**.
-  1. In the left navigation menu, select **Keys and Endpoint**.
+  1. In the left pane, select **Keys and Endpoint**.
   1. Copy one of the keys and the **Endpoint** for use later in this article.
 
   :::image type="content" source="../../../media/containers/keys-and-endpoint.png" alt-text="Screenshot of keys and endpoint location in the Azure portal.":::

@@ -45,7 +45,7 @@ monikerRange: 'doc-intel-3.1.0 || doc-intel-3.0.0'
 - The key and endpoint from the resource you create to connect your application to the Azure Document Intelligence service.
 
   1. After your resource deploys, select **Go to resource**.
-  1. In the left navigation menu, select **Keys and Endpoint**.
+  1. In the left pane, select **Keys and Endpoint**.
   1. Copy one of the keys and the **Endpoint** for use later in this article.
 
   :::image type="content" source="../../../media/containers/keys-and-endpoint.png" alt-text="Screenshot of keys and endpoint location in the Azure portal.":::

@@ -39,7 +39,7 @@ monikerRange: 'doc-intel-3.1.0 || doc-intel-3.0.0'
 - The key and endpoint from the resource you create to connect your application to the Azure Document Intelligence service.
 
   1. After your resource deploys, select **Go to resource**.
-  1. In the left navigation menu, select **Keys and Endpoint**.
+  1. In the left pane, select **Keys and Endpoint**.
   1. Copy one of the keys and the **Endpoint** for use later in this article.
 
   :::image type="content" source="../../../media/containers/keys-and-endpoint.png" alt-text="Screenshot of keys and endpoint location in the Azure portal.":::

@@ -33,7 +33,7 @@ monikerRange: 'doc-intel-3.1.0 || doc-intel-3.0.0'
 - The key and endpoint from the resource you create to connect your application to the Azure Document Intelligence service.
 
   1. After your resource deploys, select **Go to resource**.
-  1. In the left navigation menu, select **Keys and Endpoint**.
+  1. In the left pane, select **Keys and Endpoint**.
   1. Copy one of the keys and the **Endpoint** for use later in this article.
 
   :::image type="content" source="../../../media/containers/keys-and-endpoint.png" alt-text="Screenshot of keys and endpoint location in the Azure portal.":::

@@ -43,7 +43,7 @@ monikerRange: 'doc-intel-3.1.0 || doc-intel-3.0.0'
 - The key and endpoint from the resource you create to connect your application to the Azure Document Intelligence service.
 
   1. After your resource deploys, select **Go to resource**.
-  1. In the left navigation menu, select **Keys and Endpoint**.
+  1. In the left pane, select **Keys and Endpoint**.
   1. Copy one of the keys and the **Endpoint** for use later in this article.
 
   :::image type="content" source="../../../media/containers/keys-and-endpoint.png" alt-text="Screenshot of keys and endpoint location in the Azure portal.":::

@@ -26,7 +26,7 @@ monikerRange: 'doc-intel-4.0.0'
 - The key and endpoint from the resource you create to connect your application to the Azure Document Intelligence service.
 
   1. After your resource deploys, select **Go to resource**.
-  1. In the left navigation menu, select **Keys and Endpoint**.
+  1. In the left pane, select **Keys and Endpoint**.
   1. Copy one of the keys and the **Endpoint** for use later in this article.
 
   :::image type="content" source="../../../media/containers/keys-and-endpoint.png" alt-text="Screenshot of keys and endpoint location in the Azure portal.":::

@@ -38,7 +38,7 @@ ms.custom: devx-track-csharp, linux-related-content
 - The key and endpoint from the resource you create to connect your application to the Azure Document Intelligence service.
 
   1. After your resource deploys, select **Go to resource**.
-  1. In the left navigation menu, select **Keys and Endpoint**.
+  1. In the left pane, select **Keys and Endpoint**.
   1. Copy one of the keys and the **Endpoint** for use later in this article.
 
   :::image type="content" source="../../../media/containers/keys-and-endpoint.png" alt-text="Screenshot of keys and endpoint location in the Azure portal.":::

@@ -31,7 +31,7 @@ ms.custom: devx-track-csharp, linux-related-content
 - The key and endpoint from the resource you create to connect your application to the Azure Document Intelligence service.
 
   1. After your resource deploys, select **Go to resource**.
-  1. In the left navigation menu, select **Keys and Endpoint**.
+  1. In the left pane, select **Keys and Endpoint**.
   1. Copy one of the keys and the **Endpoint** for use later in this article.
 
   :::image type="content" source="../../../media/containers/keys-and-endpoint.png" alt-text="Screenshot of keys and endpoint location in the Azure portal.":::

@@ -26,7 +26,7 @@ ms.custom: devx-track-csharp, linux-related-content
 - The key and endpoint from the resource you create to connect your application to the Azure Document Intelligence service.
 
   1. After your resource deploys, select **Go to resource**.
-  1. In the left navigation menu, select **Keys and Endpoint**.
+  1. In the left pane, select **Keys and Endpoint**.
   1. Copy one of the keys and the **Endpoint** for use later in this article.
 
   :::image type="content" source="../../../media/containers/keys-and-endpoint.png" alt-text="Screenshot of keys and endpoint location in the Azure portal.":::

@@ -36,7 +36,7 @@ ms.author: lajanuar
 - The key and endpoint from the resource you create to connect your application to the Azure Document Intelligence service.
 
   1. After your resource deploys, select **Go to resource**.
-  1. In the left navigation menu, select **Keys and Endpoint**.
+  1. In the left pane, select **Keys and Endpoint**.
   1. Copy one of the keys and the **Endpoint** for use later in this article.
 
   :::image type="content" source="../../../media/containers/keys-and-endpoint.png" alt-text="Screenshot of keys and endpoint location in the Azure portal.":::

@@ -75,7 +75,7 @@ Navigate to the [Document Intelligence Studio](https://formrecognizer.appliedai.
 * **Local authentication: access by API endpoint and key**.
 
   * Retrieve your endpoint and key from the Azure portal.
-  * Go to the overview page for your resource and select **Keys and Endpoint** from the left navigation bar.
+  * Go to the overview page for your resource and select **Keys and Endpoint** from the left pane.
   * Enter the values in the appropriate fields.
 
       :::image type="content" source="../media/studio/keys-and-endpoint.png" lightbox="../media/studio/keys-and-endpoint.png" alt-text="Screenshot of the keys and endpoint page in the Azure portal.":::

@@ -644,15 +644,9 @@ AzureKeyCredential credential = new AzureKeyCredential(key);
 DocumentIntelligenceClient client = new DocumentIntelligenceClient(new Uri(endpoint), credential);
 
 //sample invoice document
+Uri uriSource = new Uri("https://raw.githubusercontent.com/Azure-Samples/cognitive-services-REST-api-samples/master/curl/form-recognizer/sample-invoice.pdf");
 
-Uri invoiceUri = new Uri ("https://raw.githubusercontent.com/Azure-Samples/cognitive-services-REST-api-samples/master/curl/form-recognizer/sample-invoice.pdf");
-
-AnalyzeDocumentContent content = new AnalyzeDocumentContent()
-{
-    UrlSource = invoiceUri
-};
-
-Operation<AnalyzeResult> operation = await client.AnalyzeDocumentAsync(WaitUntil.Completed, "prebuilt-invoice", content);
+Operation<AnalyzeResult> operation = await client.AnalyzeDocumentAsync(WaitUntil.Completed, "prebuilt-invoice", uriSource);
 
 AnalyzeResult result = operation.Value;
 
@@ -663,39 +657,39 @@ for (int i = 0; i < result.Documents.Count; i++)
     AnalyzedDocument document = result.Documents[i];
 
     if (document.Fields.TryGetValue("VendorName", out DocumentField vendorNameField)
-        && vendorNameField.Type == DocumentFieldType.String)
+        && vendorNameField.FieldType == DocumentFieldType.String)
     {
         string vendorName = vendorNameField.ValueString;
         Console.WriteLine($"Vendor Name: '{vendorName}', with confidence {vendorNameField.Confidence}");
     }
 
     if (document.Fields.TryGetValue("CustomerName", out DocumentField customerNameField)
-        && customerNameField.Type == DocumentFieldType.String)
+        && customerNameField.FieldType == DocumentFieldType.String)
     {
         string customerName = customerNameField.ValueString;
         Console.WriteLine($"Customer Name: '{customerName}', with confidence {customerNameField.Confidence}");
     }
 
     if (document.Fields.TryGetValue("Items", out DocumentField itemsField)
-        && itemsField.Type == DocumentFieldType.List)
+        && itemsField.FieldType == DocumentFieldType.List)
     {
         foreach (DocumentField itemField in itemsField.ValueList)
         {
             Console.WriteLine("Item:");
 
-            if (itemField.Type == DocumentFieldType.Dictionary)
+            if (itemField.FieldType == DocumentFieldType.Dictionary)
             {
                 IReadOnlyDictionary<string, DocumentField> itemFields = itemField.ValueDictionary;
 
                 if (itemFields.TryGetValue("Description", out DocumentField itemDescriptionField)
-                    && itemDescriptionField.Type == DocumentFieldType.String)
+                    && itemDescriptionField.FieldType == DocumentFieldType.String)
                 {
                     string itemDescription = itemDescriptionField.ValueString;
                     Console.WriteLine($"  Description: '{itemDescription}', with confidence {itemDescriptionField.Confidence}");
                 }
 
                 if (itemFields.TryGetValue("Amount", out DocumentField itemAmountField)
-                    && itemAmountField.Type == DocumentFieldType.Currency)
+                    && itemAmountField.FieldType == DocumentFieldType.Currency)
                 {
                     CurrencyValue itemAmount = itemAmountField.ValueCurrency;
                     Console.WriteLine($"  Amount: '{itemAmount.CurrencySymbol}{itemAmount.Amount}', with confidence {itemAmountField.Confidence}");
@@ -705,27 +699,26 @@ for (int i = 0; i < result.Documents.Count; i++)
     }
 
     if (document.Fields.TryGetValue("SubTotal", out DocumentField subTotalField)
-        && subTotalField.Type == DocumentFieldType.Currency)
+        && subTotalField.FieldType == DocumentFieldType.Currency)
     {
         CurrencyValue subTotal = subTotalField.ValueCurrency;
         Console.WriteLine($"Sub Total: '{subTotal.CurrencySymbol}{subTotal.Amount}', with confidence {subTotalField.Confidence}");
     }
 
     if (document.Fields.TryGetValue("TotalTax", out DocumentField totalTaxField)
-        && totalTaxField.Type == DocumentFieldType.Currency)
+        && totalTaxField.FieldType == DocumentFieldType.Currency)
     {
         CurrencyValue totalTax = totalTaxField.ValueCurrency;
         Console.WriteLine($"Total Tax: '{totalTax.CurrencySymbol}{totalTax.Amount}', with confidence {totalTaxField.Confidence}");
     }
 
     if (document.Fields.TryGetValue("InvoiceTotal", out DocumentField invoiceTotalField)
-        && invoiceTotalField.Type == DocumentFieldType.Currency)
+        && invoiceTotalField.FieldType == DocumentFieldType.Currency)
     {
         CurrencyValue invoiceTotal = invoiceTotalField.ValueCurrency;
         Console.WriteLine($"Invoice Total: '{invoiceTotal.CurrencySymbol}{invoiceTotal.Amount}', with confidence {invoiceTotalField.Confidence}");
     }
 }
-
 ```
 
 **Run your application**

@@ -118,7 +118,7 @@ Enable CORS on your storage account. Select your storage account in the Azure po
 
 Connections can be set up and shared across projects. They use an extensible provider model, so you can easily add new source/target providers.
 
-To create a new connection, select the **New Connections** (plug) icon, in the left navigation bar.
+To create a new connection, select the **New Connections** (plug) icon, in the left pane.
 
 Fill in the fields with the following values:
 
@@ -135,7 +135,7 @@ Fill in the fields with the following values:
 In the Sample Labeling tool, projects store your configurations and settings. Create a new project and fill in the fields with the following values:
 
 * **Display Name** - the project display name
-* **Security Token** - Some project settings can include sensitive values, such as keys or other shared secrets. Each project generates a security token that can be used to encrypt/decrypt sensitive project settings. You can find security tokens in the Application Settings by selecting the gear icon at the bottom of the left navigation bar.
+* **Security Token** - Some project settings can include sensitive values, such as keys or other shared secrets. Each project generates a security token that can be used to encrypt/decrypt sensitive project settings. You can find security tokens in the Application Settings by selecting the gear icon at the bottom of the left pane.
 * **Source Connection** - The Azure Blob Storage connection you created in the previous step that you would like to use for this project.
 * **Folder Path** - Optional - If your source forms are located in a folder on the blob container, specify the folder name here
 * **Document Intelligence Service Uri** - Your Document Intelligence endpoint URL.

@@ -181,7 +181,7 @@ Configure the **Project Settings** fields with the following values:
 
 1. **Display Name**. Name your project.
 
-1. **Security Token**. Each project autogenerates a security token that can be used to encrypt/decrypt sensitive project settings. You can find security tokens in the Application Settings by selecting the gear icon at the bottom of the left navigation bar.
+1. **Security Token**. Each project autogenerates a security token that can be used to encrypt/decrypt sensitive project settings. You can find security tokens in the Application Settings by selecting the gear icon at the bottom of the left pane.
 
 1. **Source connection**. The Sample Labeling tool connects to a source (your original uploaded forms) and a target (created labels and output data). Connections can be set up and shared across projects. They use an extensible provider model, so you can easily add new source/target providers.
 

@@ -29,7 +29,7 @@ Azure RBAC can be assigned to a Language resource. To grant access to an Azure r
    > [!NOTE]
    > You can also set up Azure RBAC for whole resource groups, subscriptions, or management groups. Do this by selecting the desired scope level and then navigating to the desired item. For example, selecting **Resource groups** and then navigating to a specific resource group.
 
-1. Select **Access control (IAM)** on the left navigation pane.
+1. Select **Access control (IAM)** on the left pane.
 1. Select **Add**, then select **Add role assignment**.
 1. On the **Role** tab on the next screen, select a role you want to add.
 1. On the **Members** tab, select a user, group, service principal, or managed identity.

@@ -7,4 +7,4 @@ ms.date: 11/21/2024
 ms.author: jboback
 ---
 
-When you don't need your project anymore, you can delete your project using Language Studio. Select **Projects** from the left navigation menu, select the project you want to delete, and then select **Delete** from the top menu.
+When you don't need your project anymore, you can delete your project using Language Studio. Select **Projects** from the left pane, select the project you want to delete, and then select **Delete** from the top menu.

@@ -46,7 +46,7 @@ When you trigger an autolabeling job based on a model you've trained, there's a
 >
 > `ceil(8921/1000) = ceil(8.921)`, which is 9 text records.
 
-1.  From the left navigation menu, select **Data labeling**.
+1.  From the left pane, select **Data labeling**.
 2.  Select the **Autolabel** button under the Activity pane to the right of the page.
 
 
@@ -81,7 +81,7 @@ You should see the model used, number of documents included in the autolabeling
 
 When you trigger an autolabeling job with GPT, you're charged to your Azure OpenAI resource as per your consumption. You're charged an estimate of the number of tokens in each document being autolabeled. Refer to the [Azure OpenAI pricing page](https://azure.microsoft.com/pricing/details/cognitive-services/openai-service/) for a detailed breakdown of pricing per token of different models.
 
-1.  From the left navigation menu, select **Data labeling**.
+1.  From the left pane, select **Data labeling**.
 2.  Select the **Autolabel** button under the Activity pane to the right of the page.
 
     :::image type="content" source="../media/trigger-autotag.png" alt-text="A screenshot showing how to trigger an autotag job from the activity pane." lightbox="../media/trigger-autotag.png":::

@@ -17,7 +17,7 @@ Use the following steps to set the required roles for your Language resource and
 ### Roles for your Azure AI Language resource
 
 1. Go to your storage account or Language resource in the [Azure portal](https://portal.azure.com/).
-2. Select **Access Control (IAM)** in the left navigation menu.
+2. Select **Access Control (IAM)** in the left pane.
 3. Select **Add** to **Add Role Assignments**, and choose the appropriate role for your account.
 
     You should have the **owner** or **contributor** role assigned on your Language resource.
@@ -30,7 +30,7 @@ Use the following steps to set the required roles for your Language resource and
 ### Roles for your storage account
 
 1. Go to your storage account page in the [Azure portal](https://portal.azure.com/).
-2. Select **Access Control (IAM)** in the left navigation menu.
+2. Select **Access Control (IAM)** in the left pane.
 3. Select **Add** to **Add Role Assignments**, and choose the **Storage blob data contributor** role on the storage account.
 4. Within **Assign access to**, select **Managed identity**. 
 5. Select **Select members**
@@ -41,7 +41,7 @@ Use the following steps to set the required roles for your Language resource and
 > If you skip this step, you'll have a 403 error when trying to connect to your custom project. It's important that your current user has this role to access storage account blob data, even if you're the owner of the storage account.
 > 
 1. Go to your storage account page in the [Azure portal](https://portal.azure.com/).
-2. Select **Access Control (IAM)** in the left navigation menu.
+2. Select **Access Control (IAM)** in the left pane.
 3. Select **Add** to **Add Role Assignments**, and choose the **Storage blob data contributor** role on the storage account.
 4. Within **Assign access to**, select **User, group, or service principal**. 
 5. Select **Select members**

@@ -30,7 +30,7 @@ Before you can use autolabeling with GPT, you need:
 
 When you trigger an autolabeling job with GPT, you're charged to your Azure OpenAI resource as per your consumption. You're charged an estimate of the number of tokens in each document being autolabeled. Refer to the [Azure OpenAI pricing page](https://azure.microsoft.com/pricing/details/cognitive-services/openai-service/) for a detailed breakdown of pricing per token of different models.
 
-1.  From the left navigation menu, select **Data labeling**.
+1.  From the left pane, select **Data labeling**.
 2.  Select the **Autolabel** button under the Activity pane to the right of the page.
 
     :::image type="content" source="../media/trigger-autotag.png" alt-text="A screenshot showing how to trigger an autotag job from the activity pane." lightbox="../media/trigger-autotag.png":::

@@ -19,7 +19,7 @@ Use the following steps to set the required roles for your Language resource and
 ### Roles for your Azure AI Language resource
 
 1. Go to your storage account or Language resource in the [Azure portal](https://portal.azure.com/).
-2. Select **Access Control (IAM)** in the left navigation menu.
+2. Select **Access Control (IAM)** in the left pane.
 3. Select **Add** to **Add Role Assignments**, and choose the appropriate role for your account.
 
     You should have the **owner** or **contributor** role assigned on your Language resource.
@@ -32,7 +32,7 @@ Use the following steps to set the required roles for your Language resource and
 ### Roles for your storage account
 
 1. Go to your storage account page in the [Azure portal](https://portal.azure.com/).
-2. Select **Access Control (IAM)** in the left navigation menu.
+2. Select **Access Control (IAM)** in the left pane.
 3. Select **Add** to **Add Role Assignments**, and choose the **Storage blob data contributor** role on the storage account.
 4. Within **Assign access to**, select **Managed identity**. 
 5. Select **Select members**

@@ -55,7 +55,7 @@ Before you connect to Azure Machine Learning, you need an Azure Machine Learning
 
 1.	Use the [Azure portal](https://portal.azure.com) to navigate to the Azure Blob Storage account connected to your language resource.
 2.	Ensure that the *Storage Blob Data Contributor* role is assigned to your AML workspace within the role assignments for your Azure Blob Storage account. 
-3.	Navigate to your project in [Language Studio](https://language.azure.com/). From the left navigation menu of your project, select **Data labeling**.
+3.	Navigate to your project in [Language Studio](https://language.azure.com/). From the left pane of your project, select **Data labeling**.
 4.	Select **use Azure Machine Learning to label** in either the **Data labeling** description, or under the **Activity pane**. 
 
     :::image type="content" source="./media/azure-machine-learning-selection.png" alt-text="A screenshot showing the location of the Azure Machine Learning link." lightbox="./media/azure-machine-learning-selection.png":::
@@ -110,7 +110,7 @@ After you've switched to labeling with Azure Machine Learning, You can switch ba
 
 To switch back to labeling with Language Studio:
 
-1. Navigate to your project in Azure Machine Learning and select **Data labeling** from the left navigation menu. 
+1. Navigate to your project in Azure Machine Learning and select **Data labeling** from the left pane. 
 1. Select the **Language Studio** tab and select **Switch to Language Studio**. 
 
     :::image type="content" source="./media/azure-machine-learning-studio.png" alt-text="A screenshot showing the selector for using labels from Language Studio." lightbox="./media/azure-machine-learning-studio.png":::

@@ -17,7 +17,7 @@ Use the following steps to set the required roles for your Language resource and
 ### Roles for your Azure AI Language resource
 
 1. Go to your storage account or Language resource in the [Azure portal](https://portal.azure.com/).
-2. Select **Access Control (IAM)** in the left navigation menu.
+2. Select **Access Control (IAM)** in the left pane.
 3. Select **Add** to **Add Role Assignments**, and choose the appropriate role for your account.
 
     You should have the **owner** or **contributor** role assigned on your Language resource.
@@ -30,7 +30,7 @@ Use the following steps to set the required roles for your Language resource and
 ### Roles for your storage account
 
 1. Go to your storage account page in the [Azure portal](https://portal.azure.com/).
-2. Select **Access Control (IAM)** in the left navigation menu.
+2. Select **Access Control (IAM)** in the left pane.
 3. Select **Add** to **Add Role Assignments**, and choose the **Storage blob data contributor** role on the storage account.
 4. Within **Assign access to**, select **Managed identity**. 
 5. Select **Select members**

@@ -15,6 +15,6 @@ Next you will need the key and endpoint from the resource to connect your applic
 
     :::image type="content" source="../media/portal-resource-next-steps.png" alt-text="A screenshot showing the next steps after a resource has deployed." lightbox="../media/portal-resource-next-steps.png":::
 
-1. On the screen for your resource, select **Keys and endpoint** on the left navigation menu. You will use one of your keys and your endpoint in the steps below. 
+1. On the screen for your resource, select **Keys and endpoint** on the left pane. You will use one of your keys and your endpoint in the steps below. 
 
     :::image type="content" source="../media/azure-portal-resource-credentials.png" alt-text="A screenshot showing the keys and endpoint section for a resource." lightbox="../media/azure-portal-resource-credentials.png":::

@@ -7,4 +7,4 @@ ms.date: 12/19/2023
 ms.author: jboback
 ---
 
- When you don't need your project anymore, you can delete your project using Language Studio. Select **Projects** from the left navigation menu, select the project you want to delete, and then select **Delete** from the top menu.
+ When you don't need your project anymore, you can delete your project using Language Studio. Select **Projects** from the left pane, select the project you want to delete, and then select **Delete** from the top menu.

@@ -37,7 +37,7 @@ This tutorial will include creating a **chit chat** knowledge base and **email c
     
     :::image type="content" source="../media/chit-chat.png" alt-text="A screenshot of the chit chat popup." lightbox="../media/chit-chat.png":::
     
-5. Go to **Deploy knowledge base** from the left navigation menu and select **Deploy** and confirm the popup that shows up.
+5. Go to **Deploy knowledge base** from the left pane and select **Deploy** and confirm the popup that shows up.
 
 You are now done with deploying your knowledge base for chit chat. You can explore the type of questions and answers to expect in the **Edit knowledge base** page.
 

@@ -32,7 +32,7 @@ For a client application, such as a bot with the [Azure AI Bot Service](/azure/b
 The project default answer is returned when no answer is returned from custom question answering.
 
 1. Sign in to the [Language Studio](https://language.azure.com). Go to custom question answering and select your project from the list.
-1. Select **Settings** from the left navigation bar.
+1. Select **Settings** from the left pane.
 1. Change the value of **Default answer when no answer found** > Select **Save**.
 
 > [!div class="mx-imgBorder"]

@@ -52,7 +52,7 @@ From the main custom question answering page in Language Studio you can:
 
 ## Manage sources
 
-1. Select **Manage sources** in the left navigation bar.
+1. Select **Manage sources** in the left pane.
 
 1.  There are three types of sources: **URLS**, **Files**, and **Chitchat**