portal-nav wording corrections

Author: LauraKellerGitHub

articles/app-service/configure-authentication-provider-aad.md

@@ -36,7 +36,7 @@ Follow these best practices when setting up your app and authentication:
 
 ## <a name="express"> </a>Configure with express settings
 
-1. On the [Azure portal] menu or from the **Home** page, go to App Services and select your app.
+1. In the [Azure portal], search for and select **App Services**, and then select your app.
 1. In the left pane, under **Settings** select **Authentication / Authorization** and make sure that **App Service Authentication** is **On**.
 1. Select **Azure Active Directory**, and then under **Management Mode** select **Express**.
 1. Select **OK** to register the App Service app in Azure Active Directory. A new app registration is created.
@@ -72,7 +72,7 @@ You'll need the following information when you configure your App Service app:
 
 Perform the following steps:
 
-1. Sign in to the [Azure portal] and go to your App Service app. Note your app's **URL**. You'll use it to configure your Azure Active Directory app registration.
+1. Sign in to the [Azure portal], search for and select **App Services**, and then select your app. Note your app's **URL**. You'll use it to configure your Azure Active Directory app registration.
 1. Select **Azure Active Directory** > **App registrations** > **New registration**.
 1. In the **Register an application** page, enter a **Name** for your app registration.
 1. In **Redirect URI**, select **Web** and enter the URL of your App Service app and append the path `/.auth/login/aad/callback`. For example, `https://contoso.azurewebsites.net/.auth/login/aad/callback`. 
@@ -93,7 +93,7 @@ Perform the following steps:
 
 ### <a name="secrets"> </a>Add Azure Active Directory information to your App Service app
 
-1. On the [Azure portal] menu or from the **Home** page, go to your App Service app. 
+1. In the [Azure portal], search for and select **App Services**, and then select your app. 
 1. In the left pane, under **Settings**, select **Authentication / Authorization** and make sure that **App Service Authentication** is **On**.
 1. (Optional) By default, App Service authentication allows unauthenticated access to your app. To enforce user authentication, set **Action to take when request is not authenticated** to **Log in with Azure Active Directory**.
 1. Under Authentication Providers, select **Azure Active Directory**.
@@ -116,7 +116,7 @@ You're now ready to use Azure Active Directory for authentication in your App Se
 
 You can register native clients to allow authentication using a client library such as the **Active Directory Authentication Library**.
 
-1. On the [Azure portal] menu or from the **Home** page, select **Active Directory** > **App registrations** > **New registration**.
+1. In the [Azure portal], select **Active Directory** > **App registrations** > **New registration**.
 1. In the **Register an application** page, enter a **Name** for your app registration.
 1. In **Redirect URI**, select **Public client (mobile & desktop)** and enter the URL of your App Service app and append the path `/.auth/login/aad/callback`. For example, `https://contoso.azurewebsites.net/.auth/login/aad/callback`.
 1. Select **Create**.

articles/app-service/configure-common.md

@@ -26,7 +26,7 @@ This topic explains how to configure common settings for web apps, mobile back e
 
 In App Service, app settings are variables passed as environment variables to the application code. For Linux apps and custom containers, App Service passes app settings to the container using the `--env` flag to set the environment variable in the container.
 
-On the [Azure portal] menu or from the **Home** page, go to your app's management page. In the app's left menu, select **Configuration** > **Application settings**.
+In the [Azure portal], search for and select **App Services**, and then select your app. In the app's left menu, select **Configuration** > **Application settings**.
 
 ![Application Settings](./media/configure-common/open-ui.png)
 
@@ -87,7 +87,7 @@ App settings have the following JSON formatting:
 
 ## Configure connection strings
 
-On the [Azure portal] menu or from the **Home** page, go to the app's management page. In the app's left menu, select **Configuration** > **Application settings**.
+In the [Azure portal], search for and select **App Services**, and then select your app. In the app's left menu, select **Configuration** > **Application settings**.
 
 ![Application Settings](./media/configure-common/open-ui.png)
 
@@ -158,7 +158,7 @@ Connection strings have the following JSON formatting:
 
 ## Configure general settings
 
-In the [Azure portal] menu or from the **Home** page, go to the app's management page. In the app's left menu, select **Configuration** > **General settings**.
+In the [Azure portal], search for and select **App Services**, and then select your app. In the app's left menu, select **Configuration** > **General settings**.
 
 ![General settings](./media/configure-common/open-general.png)
 
@@ -181,7 +181,7 @@ Here, you can configure some common settings for the app. Some settings require
 
 This setting is only for Windows apps.
 
-On the [Azure portal] menu or from the **Home** page, go to your app's management page. In the app's left menu, select **Configuration** > **Default documents**.
+In the [Azure portal], search for and select **App Services**, and then select your app. In the app's left menu, select **Configuration** > **Default documents**.
 
 ![Default documents](./media/configure-common/open-documents.png)
 
@@ -191,7 +191,7 @@ If the app uses modules that route based on URL instead of serving static conten
 
 ## Configure path mappings
 
-On the [Azure portal] menu or from the **Home** page, go to your app's management page. In the app's left menu, select **Configuration** > **Path mappings**.
+In the [Azure portal], search for and select **App Services**, and then select your app. In the app's left menu, select **Configuration** > **Path mappings**.
 
 ![Path mappings](./media/configure-common/open-path.png)
 

articles/app-service/deploy-staging-slots.md

@@ -38,7 +38,7 @@ To scale your app to a different tier, make sure that the target tier supports t
 ## Add a slot
 The app must be running in the **Standard**, **Premium**, or **Isolated** tier in order for you to enable multiple deployment slots.
 
-1. On the [Azure portal](https://portal.azure.com/) menu or from the **Home** page, open your app's [resource page](../azure-resource-manager/manage-resources-portal.md#manage-resources).
+1. in the [Azure portal](https://portal.azure.com/), open your app's [resource page](../azure-resource-manager/manage-resources-portal.md#manage-resources).
 
 2. In the left pane, select **Deployment slots** > **Add Slot**.
 
@@ -247,7 +247,7 @@ After the setting is saved, the specified percentage of clients is randomly rout
 After a client is automatically routed to a specific slot, it's "pinned" to that slot for the life of that client session. On the client browser, you can see which slot your session is pinned to by looking at the `x-ms-routing-name` cookie in your HTTP headers. A request that's routed to the "staging" slot has the cookie `x-ms-routing-name=staging`. A request that's routed to the production slot has the cookie `x-ms-routing-name=self`.
 
    > [!NOTE]
-   > Next to the Azure Portal, you can also use the [`az webapp traffic-routing set`](/cli/azure/webapp/traffic-routing#az-webapp-traffic-routing-set) command in the Azure CLI to set the routing percentages from CI/CD tools like DevOps pipelines or other automation systems.
+   > Next to the Azure portal, you can also use the [`az webapp traffic-routing set`](/cli/azure/webapp/traffic-routing#az-webapp-traffic-routing-set) command in the Azure CLI to set the routing percentages from CI/CD tools like DevOps pipelines or other automation systems.
    > 
 
 ### Route production traffic manually