@@ -233,7 +233,7 @@ Alternatively, if you aren't ready to commit changes, you can save the debug ses
 
 1. Select **OK** to confirm that you wish to update your skillset.
 
-1. Close Debug session and open **Indexers** from the left navigation pane.
+1. Close Debug session and open **Indexers** from the left pane.
 
 1. Select 'clinical-trials-idxr'.
 
@@ -245,7 +245,7 @@ Alternatively, if you aren't ready to commit changes, you can save the debug ses
 
 When the indexer has finished running, there should be a green checkmark and the word Success next to the time stamp for the latest run in the **Execution history** tab. To ensure that the changes have been applied:
 
-1. In the left navigation pane, open **Indexes**.
+1. In the left pane, open **Indexes**.
 
 1. Select 'clinical-trials' index and in the Search explorer tab, enter this query string: `$select=metadata_storage_path, organizations, locations&$count=true` to return fields for specific documents (identified by the unique `metadata_storage_path` field).
 

@@ -65,15 +65,15 @@ Follow the steps in this article using sample data and a knowledge store as [cre
 
 ## Check table relationships
 
-1. Select on the Model tile on the left navigation pane and validate that Power BI shows relationships between all three tables.
+1. Select on the Model tile on the left pane and validate that Power BI shows relationships between all three tables.
 
    ![Validate relationships](media/knowledge-store-connect-power-bi/powerbi-relationships.png "Validate relationships")
 
 1. Double-click each relationship and make sure that the **Cross-filter direction** is set to **Both**.  This enables your visuals to refresh when a filter is applied.
 
 ## Build a report
 
-1. Select on the Report tile on the left navigation pane to explore data through visualizations. For text fields, tables and cards are useful visualizations.
+1. Select on the Report tile on the left pane to explore data through visualizations. For text fields, tables and cards are useful visualizations.
 
 1. Choose fields from each of the three tables to fill in the table or card.
 

@@ -145,7 +145,7 @@ In the **Overview** page, open the **Indexers** tab in the middle of the page, a
 
 1. In the Azure portal, [open the Storage account](https://portal.azure.com/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Storage%2storageAccounts/) used to create the knowledge store.
 
-1. In the storage account's left navigation pane, select **Storage browser** to view the new tables. 
+1. In the storage account's left pane, select **Storage browser** to view the new tables. 
 
    You should see three tables, one for each projection that was offered in the "Save enrichments" section of the "Add enrichments" page.
 

@@ -98,7 +98,7 @@ Indexers can connect to a file share using the following connections.
 | Full access storage account connection string |
 |-----------------------------------------------|
 |`{ "connectionString" : "DefaultEndpointsProtocol=https;AccountName=<your storage account>;AccountKey=<your account key>;" }` |
-| You can get the connection string from the Storage account page in Azure portal by selecting **Access keys** in the left navigation pane. Make sure to select a full connection string and not just a key. |
+| You can get the connection string from the Storage account page in Azure portal by selecting **Access keys** in the left pane. Make sure to select a full connection string and not just a key. |
 
 ## Add search fields to an index
 

@@ -67,7 +67,7 @@ You need this step if you have more than one subscription or tenant.
 
    1. Navigate to your search service.
 
-   1. Select **Access Control (IAM)** in the left navigation pane.
+   1. Select **Access Control (IAM)** in the left pane.
 
    1. Select **+ Add** > **Add role assignment**.
 

@@ -129,7 +129,7 @@ The indexer drives the indexing process. It specifies the data source name, a ta
 
 ## Monitor status
 
-Select **Indexers** from the left navigation pane to monitor status, and then select the indexer. Skills-based indexing takes longer than text-based indexing, especially OCR and image analysis.
+Select **Indexers** from the left pane to monitor status, and then select the indexer. Skills-based indexing takes longer than text-based indexing, especially OCR and image analysis.
 
   :::image type="content" source="media/search-get-started-skillset/indexer-notification.png" alt-text="Screenshot of the indexer status page." border="true":::
 

@@ -155,7 +155,7 @@ The following screenshot highlights where **Add index**, **Import data**, and **
 
 :::image type="content" source="media/search-what-is-an-index/add-index.png" alt-text="Screenshot of the options to add an index." border="true":::
 
-After an index is created, you can find it again on the **Indexes** page from the left navigation pane.
+After an index is created, you can find it again on the **Indexes** page from the left pane.
 
 > [!TIP]
 > After creating an index in the Azure portal, you can copy the JSON representation and add it to your application code.

@@ -124,7 +124,7 @@ Indexers can connect to a blob container using the following connections.
 | Full access storage account connection string |
 |-----------------------------------------------|
 |`{ "connectionString" : "DefaultEndpointsProtocol=https;AccountName=<your storage account>;AccountKey=<your account key>;" }` |
-| You can get the connection string from the Storage account page in Azure portal by selecting **Access keys** in the left navigation pane. Make sure to select a full connection string and not just a key. |
+| You can get the connection string from the Storage account page in Azure portal by selecting **Access keys** in the left pane. Make sure to select a full connection string and not just a key. |
 
 | Managed identity connection string |
 |------------------------------------|

@@ -91,7 +91,7 @@ Avoid port numbers in the endpoint URL. If you include the port number, the conn
 | Full access connection string |
 |-----------------------------------------------|
 |`{ "connectionString" : "AccountEndpoint=https://<Cosmos DB account name>.documents.azure.com;AccountKey=<Cosmos DB auth key>;Database=<Cosmos DB database id>;ApiKind=MongoDb" }` |
-| You can get the connection string from the Azure Cosmos DB account page in Azure portal by selecting **Keys** in the left navigation pane. Make sure to select a full connection string and not just a key.  |
+| You can get the connection string from the Azure Cosmos DB account page in Azure portal by selecting **Keys** in the left pane. Make sure to select a full connection string and not just a key.  |
 
 | Managed identity connection string |
 |------------------------------------|

@@ -99,7 +99,7 @@ Avoid port numbers in the endpoint URL. If you include the port number, the conn
 | Full access connection string |
 |-----------------------------------------------|
 |`{ "connectionString" : "AccountEndpoint=https://<Cosmos DB account name>.documents.azure.com;AccountKey=<Cosmos DB auth key>;Database=<Cosmos DB database id>;ApiKind=MongoDb" }` |
-| You can get the *Cosmos DB auth key* from the Azure Cosmos DB account page in the Azure portal by selecting **Connection String** in the left navigation pane. Make sure to copy **Primary Password** and replace *Cosmos DB auth key* value with it. |
+| You can get the *Cosmos DB auth key* from the Azure Cosmos DB account page in the Azure portal by selecting **Connection String** in the left pane. Make sure to copy **Primary Password** and replace *Cosmos DB auth key* value with it. |
 
 | Managed identity connection string |
 |------------------------------------|

@@ -147,7 +147,7 @@ Avoid port numbers in the endpoint URL. If you include the port number, the conn
 | Full access connection string |
 |-----------------------------------------------|
 |`{ "connectionString" : "AccountEndpoint=https://<Cosmos DB account name>.documents.azure.com;AccountKey=<Cosmos DB auth key>;Database=<Cosmos DB database id>`" }` |
-| You can get the connection string from the Azure Cosmos DB account page in the Azure portal by selecting **Keys** in the left navigation pane. Make sure to select a full connection string and not just a key. |
+| You can get the connection string from the Azure Cosmos DB account page in the Azure portal by selecting **Keys** in the left pane. Make sure to select a full connection string and not just a key. |
 
 | (Modern approach) Managed identity connection string for NoSQL accounts |
 |------------------------------------------------------------------------------|

@@ -69,9 +69,9 @@ You should have an Azure Function app that contains the decryption logic and an
 
 1. Navigate to your Azure Key Vault service in the Azure portal. [Create an access policy](/azure/key-vault/general/assign-access-policy-portal) in the Azure Key Vault that grants key access to the custom skill.
 
-1. On the left navigation pane, select **Access policies**, and then select **+ Create** to start the **Create an access policy** wizard.
+1. On the left pane, select **Access policies**, and then select **+ Create** to start the **Create an access policy** wizard.
 
-    :::image type="content" source="media/indexing-encrypted-blob-files/keyvault-access-policies.png" alt-text="Screenshot of the Access Policy command in the left navigation pane." border="true":::
+    :::image type="content" source="media/indexing-encrypted-blob-files/keyvault-access-policies.png" alt-text="Screenshot of the Access Policy command in the left pane." border="true":::
 
 1. On the **Permissions** page under **Configure from template**, select **Azure Data Lake Storage or Azure Storage**.
 

@@ -147,7 +147,7 @@ Indexers can connect to a blob container using the following connections.
 | Full access storage account connection string |
 |-----------------------------------------------|
 |`{ "connectionString" : "DefaultEndpointsProtocol=https;AccountName=<your storage account>;AccountKey=<your account key>;" }` |
-| You can get the connection string from the Storage account page in Azure portal by selecting **Access keys** in the left navigation pane. Make sure to select a full connection string and not just a key. |
+| You can get the connection string from the Storage account page in Azure portal by selecting **Access keys** in the left pane. Make sure to select a full connection string and not just a key. |
 
 | Managed identity connection string |
 |------------------------------------|

@@ -128,7 +128,7 @@ Indexers can connect to a table using the following connections.
 | Full access storage account connection string |
 |-----------------------------------------------|
 |`{ "connectionString" : "DefaultEndpointsProtocol=https;AccountName=<your storage account>;AccountKey=<your account key>;" }` |
-| You can get the connection string from the Storage account page in Azure portal by selecting **Access keys** in the left navigation pane. Make sure to select a full connection string and not just a key. |
+| You can get the connection string from the Storage account page in Azure portal by selecting **Access keys** in the left pane. Make sure to select a full connection string and not just a key. |
 
 | Managed identity connection string |
 |------------------------------------|

@@ -56,7 +56,7 @@ Schedules are specified in an indexer definition. To set up a schedule, you can
 ### [**Azure portal**](#tab/portal)
 
 1. Sign in to the [Azure portal](https://portal.azure.com) and open the search service page.
-1. On the left navigation pane, select **Indexers**.
+1. On the left pane, select **Indexers**.
 1. Open an indexer.
 1. Select **Settings**.
 1. Scroll down to **Schedule**, and then choose Hourly, Daily, or Custom to set a specific date, time, or custom interval.

@@ -49,7 +49,7 @@ This article explains how to find the IP address of your search service and conf
 
 Client applications that push indexing and query requests to the search service must be represented in an IP range. On Azure, you can generally determine the IP address by pinging the FQDN of a service (for example, `ping <your-search-service-name>.search.windows.net` returns the IP address of a search service).
 
-Add your client IP address to allow access to the service from the Azure portal on your current computer. Navigate to the **Networking** section on the left navigation pane. Change **Public Network Access** to **Selected networks**, and then check **Add your client IP address** under **Firewall**.
+Add your client IP address to allow access to the service from the Azure portal on your current computer. Navigate to the **Networking** section on the left pane. Change **Public Network Access** to **Selected networks**, and then check **Add your client IP address** under **Firewall**.
 
    :::image type="content" source="media\service-configure-firewall\azure-portal-firewall.png" alt-text="Screenshot of adding client ip to search service firewall" border="true":::
 
@@ -122,7 +122,7 @@ You can get this IP address range from the `AzureCognitiveSearch` service tag.
 
 Now that you have the necessary IP addresses, you can set up the inbound rules. The easiest way to add IP address ranges to a storage account's firewall rule is through the Azure portal. 
 
-1. Locate the storage account on the Azure portal and open **Networking** on the left navigation pane.
+1. Locate the storage account on the Azure portal and open **Networking** on the left pane.
 
 1. In the **Firewall and virtual networks** tab, choose **Selected networks**.
 

@@ -142,7 +142,7 @@ When you complete the steps in this section, you have a shared private link that
 
 1. Sign in to the [Azure portal](https://portal.azure.com) and [find your search service](https://portal.azure.com/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Search%2FsearchServices).
 
-1. Under **Settings** on the left navigation pane, select **Networking**.
+1. Under **Settings** on the left pane, select **Networking**.
 
 1. On the **Shared Private Access** page, select **+ Add Shared Private Access**.
 

@@ -45,7 +45,7 @@ In Azure AI Search, indexers that access Azure blobs can use the [trusted servic
 
 1. Sign in to the [Azure portal](https://portal.azure.com) and [find your storage account](https://portal.azure.com/#blade/HubsExtension/BrowseResourceBlade/resourceType/Microsoft.Storage%2storageAccounts/).
 
-1. In the left navigation pane under **Security + networking**, select **Networking**.
+1. In the left pane under **Security + networking**, select **Networking**.
 
 1. On the **Firewalls and virtual networks** tab, allow access from **Selected networks**.
 
@@ -61,7 +61,7 @@ In Azure AI Search, indexers that access Azure blobs can use the [trusted servic
 
 A system managed identity is a Microsoft Entra service principal. The assignment needs **Storage Blob Data Reader** at a minimum.
 
-1. In the left navigation pane under **Access Control**, view all role assignments and make sure that **Storage Blob Data Reader** is assigned to the search service system identity.
+1. In the left pane under **Access Control**, view all role assignments and make sure that **Storage Blob Data Reader** is assigned to the search service system identity.
 
 1. Add **Storage Blob Data Contributor** if write access is required.
 

@@ -236,7 +236,7 @@ Your code runs locally in Visual Studio, connecting to your search service on Az
 
 Use Azure portal to verify object creation, and then use **Search explorer** to query the index.
 
-1. Sign in to the [Azure portal](https://portal.azure.com), and in your search service left navigation pane, open each page in turn to verify the object is created. **Indexes**, **Indexers**, and **Data Sources** will have "hotels-sql-idx", "hotels-sql-indexer", and "hotels-sql-ds", respectively.
+1. Sign in to the [Azure portal](https://portal.azure.com), and in your search service left pane, open each page in turn to verify the object is created. **Indexes**, **Indexers**, and **Data Sources** will have "hotels-sql-idx", "hotels-sql-indexer", and "hotels-sql-ds", respectively.
 
 1. On the Indexes tab, select the hotels-sql-idx index. On the hotels page, **Search explorer** is the first tab.
 

@@ -238,7 +238,7 @@ It's not possible to use [customer-managed key encryption](search-security-manag
 
 1. Navigate to your search service page in Azure portal.
 
-1. On the left navigation pane, select **Access control (IAM)**, and then select the **Role assignments** tab.
+1. On the left pane, select **Access control (IAM)**, and then select the **Role assignments** tab.
 
 1. In the **Role** filter, select the roles that have permission to view or manage keys (Owner, Contributor, Search Service Contributor). The resulting security principals assigned to those roles have key permissions on your search service.
 

@@ -44,7 +44,7 @@ The default failure mode for unauthorized requests is `http401WithBearerChalleng
 
 1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to your search service.
 
-1. Select **Settings** and then select **Keys** in the left navigation pane.
+1. Select **Settings** and then select **Keys** in the left pane.
 
    :::image type="content" source="media/search-security-rbac/search-security-enable-roles.png" lightbox="media/search-security-rbac/search-security-enable-roles.png" alt-text="Screenshot of the keys page with authentication options." border="true":::
 
@@ -149,7 +149,7 @@ To disable role-based access control in the Azure portal:
 
 1. Sign in to the [Azure portal](https://portal.azure.com) and open the search service page.
 
-1. Select **Settings** and then select **Keys** in the left navigation pane.
+1. Select **Settings** and then select **Keys** in the left pane.
 
 1. Select **API Keys**.
 

@@ -45,7 +45,7 @@ The following steps work for all role assignments.
 
 1. [Enable role-based access](search-security-enable-roles.md).
 
-1. Select **Access Control (IAM)** in the left navigation pane.
+1. Select **Access Control (IAM)** in the left pane.
 
 1. Select **+ Add** > **Add role assignment** to start the **Add role assignment** wizard.
 

@@ -384,7 +384,7 @@ var indexStats = await indexClient.GetIndexStatisticsAsync(indexName);
 
 ### Azure portal
 
-In the Azure portal, from the left navigation pane, and find the **optimize-indexing** index in the **Indexes** list.
+In the Azure portal, from the left pane, and find the **optimize-indexing** index in the **Indexes** list.
 
 :::image type="content" source="media/tutorial-optimize-data-indexing/portal-output.png" alt-text="Screenshow that shows a list of Azure AI Search indexes.":::