Merge pull request #230837 from spelluru/egridnames0315

removing event-grid from file names

Author: v-regandowner

articles/api-management/how-to-event-grid.md

@@ -51,7 +51,7 @@ Once the deployment has succeeded (it might take a few minutes), open a browser
 
 You should see the sample app rendered with no event messages displayed.
 
-[!INCLUDE [event-grid-register-provider-portal.md](../../includes/event-grid-register-provider-portal.md)]
+[!INCLUDE [event-grid-register-provider-portal.md](../../articles/event-grid/includes/register-provider.md)]
 
 ## Subscribe to API Management events
 

articles/azure-app-configuration/howto-app-configuration-event.md

@@ -72,7 +72,7 @@ The deployment may take a few minutes to complete. After the deployment has succ
 
 You should see the site with no messages currently displayed.
 
-[!INCLUDE [event-grid-register-provider-cli.md](../../includes/event-grid-register-provider-cli.md)]
+[!INCLUDE [register-provider-cli.md](../../articles/event-grid/includes/register-provider-cli.md)]
 
 ## Subscribe to your App Configuration store
 

articles/azure-app-configuration/howto-backup-config-store.md

@@ -95,7 +95,7 @@ az storage account create -n $storageName -g $resourceGroupName -l westus --sku
 az storage queue create --name $queueName --account-name $storageName --auth-mode login
 ```
 
-[!INCLUDE [event-grid-register-provider-cli.md](../../includes/event-grid-register-provider-cli.md)]
+[!INCLUDE [register-provider-cli.md](../../articles/event-grid/includes/register-provider-cli.md)]
 
 ## Subscribe to your App Configuration store events
 
@@ -249,7 +249,7 @@ If you don't see the new setting in your secondary store:
 - Make sure the backup function was triggered *after* you created the setting in your primary store.
 - It's possible that Event Grid couldn't send the event notification to the queue in time. Check if your queue still contains the event notification from your primary store. If it does, trigger the backup function again.
 - Check [Azure Functions logs](../azure-functions/functions-create-scheduled-function.md#test-the-function) for any errors or warnings.
-- Use the [Azure portal](../azure-functions/functions-how-to-use-azure-function-app-settings.md#get-started-in-the-azure-portal) to ensure that the Azure function app contains correct values for the application settings that Azure Functions is trying to read.
+- Use the [Azure portal](../azure-functions/functions-how-to-use-azure-function-app-settings.md#get-started-in-the-azure-portal) to ensure that the Azure function app contains correct values for the application settings that the Azure function is trying to read.
 - You can also set up monitoring and alerting for Azure Functions by using [Azure Application Insights](../azure-functions/functions-monitoring.md?tabs=cmd).
 
 ## Clean up resources

articles/azure-cache-for-redis/cache-event-grid-quickstart-cli.md

@@ -64,7 +64,7 @@ The deployment may take a few minutes to complete. After the deployment has succ
 
 You should see the site with no messages currently displayed.
 
-[!INCLUDE [event-grid-register-provider-cli.md](../../includes/event-grid-register-provider-cli.md)]
+[!INCLUDE [register-provider-cli.md](../../articles/event-grid/includes/register-provider-cli.md)]
 
 ## Subscribe to your Azure Cache for Redis instance
 

articles/azure-cache-for-redis/cache-event-grid-quickstart-portal.md

@@ -29,21 +29,21 @@ Before subscribing to the events for the cache instance, let's create the endpoi
 
 1. Select **Deploy to Azure** in GitHub README to deploy the solution to your subscription.
 
-:::image type="content" source="media/cache-event-grid-portal/deploy-to-azure.png" alt-text="Deploy to Azure button.":::
+    :::image type="content" source="media/cache-event-grid-portal/deploy-to-azure.png" alt-text="Deploy to Azure button.":::
 
 1. On the **Custom deployment** page, do the following steps:
-    1. For **Resource group**, select the resource group that you created when creating the cache instance. It will be easier for you to clean up after you are done with the tutorial by deleting the resource group.  
+    1. For **Resource group**, select the resource group that you created when creating the cache instance. It will be easier for you to clean up after you're done with the tutorial by deleting the resource group.  
     2. For **Site Name**, enter a name for the web app.
     3. For **Hosting plan name**, enter a name for the App Service plan to use for hosting the web app.
     4. Select the check box for **I agree to the terms and conditions stated above**.
     5. Select **Purchase**.
 
     | Setting      | Suggested value  | Description |
     | ------------ |  ------- | -------------------------------------------------- |
-    | **Subscription** | Drop down and select your subscription. | The subscription under which to create this web app. |
+    | **Subscription** | Drop down and select your subscription. | The subscription in which you want to create this web app. |
     | **Resource group** | Drop down and select a resource group, or select **Create new** and enter a new resource group name. | By putting all your app resources in one resource group, you can easily manage or delete them together. |
-    | **Site Name** | Enter a name for your web app. | This value cannot be empty. |
-    | **Hosting plan name** | Enter a name for the App Service plan to use for hosting the web app. | This value cannot be empty. |
+    | **Site Name** | Enter a name for your web app. | This value can't be empty. |
+    | **Hosting plan name** | Enter a name for the App Service plan to use for hosting the web app. | This value can't be empty. |
 
 1. Select Alerts (bell icon) in the portal, and then select **Go to resource group**.
 
@@ -57,15 +57,16 @@ Before subscribing to the events for the cache instance, let's create the endpoi
 
     :::image type="content" source="media/cache-event-grid-portal/blank-event-grid-viewer.png" alt-text="Empty Event Grid Viewer site.":::
 
-[!INCLUDE [event-grid-register-provider-portal.md](../../includes/event-grid-register-provider-portal.md)]
+[!INCLUDE [register-provider.md](../../articles/event-grid/includes/register-provider.md)]
+
 
 ## Subscribe to the Azure Cache for Redis instance
 
 In this step, you'll subscribe to a topic to tell Event Grid which events you want to track, and where to send the events.
 
 1. In the portal, navigate to your cache instance that you created earlier.
 1. On the **Azure Cache for Redis** page, select **Events** on the left menu.
-1. Select **Web Hook**. You are sending events to your viewer app using a web hook for the endpoint.
+1. Select **Web Hook**. You're sending events to your viewer app using a web hook for the endpoint.
 
      :::image type="content" source="media/cache-event-grid-portal/event-grid-web-hook.png" alt-text="Azure portal Events page.":::
 

articles/azure-resource-manager/management/azure-subscription-service-limits.md

@@ -281,7 +281,7 @@ The following table details the features and limits of the Basic, Standard, and
 
 ## Event Grid limits
 
-[!INCLUDE [event-grid-limits](../../../includes/event-grid-limits.md)]
+[!INCLUDE [event-grid-limits](../../../articles/event-grid/includes/limits.md)]
 
 ## Event Hubs limits
 [!INCLUDE [event-hubs-limits](../../../includes/event-hubs-limits.md)]

articles/azure-signalr/signalr-howto-event-grid-integration.md

@@ -69,7 +69,7 @@ Once the SignalR Service has been created, the Azure CLI returns output similar
 
 ## Create an event endpoint
 
-In this section, you use a Resource Manager template located in a GitHub repository to deploy a pre-built sample web application to Azure App Service. Later, you subscribe to your registry's Event Grid events and specify this app as the endpoint to which the events are sent.
+In this section, you use a Resource Manager template located in a GitHub repository to deploy a prebuilt sample web application to Azure App Service. Later, you subscribe to your registry's Event Grid events and specify this app as the endpoint to which the events are sent.
 
 To deploy the sample app, set `SITE_NAME` to a unique name for your web app, and execute the following commands. The site name must be unique within Azure because it forms part of the fully qualified domain name (FQDN) of the web app. In a later section, you navigate to the app's FQDN in a web browser to view your registry's events.
 
@@ -86,11 +86,11 @@ Once the deployment succeeds (it might take a few minutes), open your browser, a
 
 `http://<your-site-name>.azurewebsites.net`
 
-[!INCLUDE [event-grid-register-provider-cli.md](../../includes/event-grid-register-provider-cli.md)]
+[!INCLUDE [register-provider-cli.md](../../articles/event-grid/includes/register-provider-cli.md)]
 
 ## Subscribe to registry events
 
-In Event Grid, you subscribe to a *topic* to tell it which events you want to track, and where to send them. The command [az eventgrid event-subscription create][az-eventgrid-event-subscription-create] subscribes to the Azure SignalR Service you created and specifies your web app's URL as the endpoint to which it should send events. The environment variables you populated in earlier sections are reused here, so no edits are required.
+In Event Grid, you subscribe to a *topic* to tell it which events you want to track, and where to send them. The command [`az eventgrid event-subscription create`][az-eventgrid-event-subscription-create] subscribes to the Azure SignalR Service you created and specifies your web app's URL as the endpoint to which it should send events. The environment variables you populated in earlier sections are reused here, so no edits are required.
 
 ```azurecli-interactive
 SIGNALR_SERVICE_ID=$(az signalr show --resource-group $RESOURCE_GROUP_NAME --name $SIGNALR_NAME --query id --output tsv)

articles/container-registry/container-registry-event-grid-quickstart.md

@@ -69,7 +69,7 @@ Once the registry has been created, the Azure CLI returns output similar to the
 
 ## Create an event endpoint
 
-In this section, you use a Resource Manager template located in a GitHub repository to deploy a pre-built sample web application to Azure App Service. Later, you subscribe to your registry's Event Grid events and specify this app as the endpoint to which the events are sent.
+In this section, you use a Resource Manager template located in a GitHub repository to deploy a prebuilt sample web application to Azure App Service. Later, you subscribe to your registry's Event Grid events and specify this app as the endpoint to which the events are sent.
 
 To deploy the sample app, set `SITE_NAME` to a unique name for your web app, and execute the following commands. The site name must be unique within Azure because it forms part of the fully qualified domain name (FQDN) of the web app. In a later section, you navigate to the app's FQDN in a web browser to view your registry's events.
 
@@ -90,11 +90,11 @@ You should see the sample app rendered with no event messages displayed:
 
 ![Web browser showing sample web app with no events displayed][sample-app-02]
 
-[!INCLUDE [event-grid-register-provider-cli.md](../../includes/event-grid-register-provider-cli.md)]
+[!INCLUDE [register-provider-cli.md](../../articles/event-grid/includes/register-provider-cli.md)]
 
 ## Subscribe to registry events
 
-In Event Grid, you subscribe to a *topic* to tell it which events you want to track, and where to send them. The following [az eventgrid event-subscription create][az-eventgrid-event-subscription-create] command subscribes to the container registry you created, and specifies your web app's URL as the endpoint to which it should send events. The environment variables you populated in earlier sections are reused here, so no edits are required.
+In Event Grid, you subscribe to a *topic* to tell it which events you want to track, and where to send them. The following [`az eventgrid event-subscription create`][az-eventgrid-event-subscription-create] command subscribes to the container registry you created, and specifies your web app's URL as the endpoint to which it should send events. The environment variables you populated in earlier sections are reused here, so no edits are required.
 
 ```azurecli-interactive
 ACR_REGISTRY_ID=$(az acr show --name $ACR_NAME --query id --output tsv)
@@ -147,7 +147,7 @@ Execute the following Azure CLI command to build a container image from the cont
 az acr build --registry $ACR_NAME --image myimage:v1 -f Dockerfile https://github.com/Azure-Samples/acr-build-helloworld-node.git#main
 ```
 
-You should see output similar to the following while ACR Tasks builds and then pushes your image. The following sample output has been truncated for brevity.
+You should see output similar to the following while ACR Tasks build and then pushes your image. The following sample output has been truncated for brevity.
 
 ```output
 Sending build context to ACR...
@@ -163,7 +163,7 @@ Step 1/5 : FROM node:9-alpine
 ...
 ```
 
-To verify that the built image is in your registry, execute the following command to view the tags in the "myimage" repository:
+To verify that the built image is in your registry, execute the following command to view the tags in the `myimage` repository:
 
 ```azurecli-interactive
 az acr repository show-tags --name $ACR_NAME --repository myimage

articles/event-grid/auth0-how-to.md

@@ -21,7 +21,7 @@ To send Auth0 events to Azure:
 5. [Subscribe to events](#subscribe-to-events).
 
 
-[!INCLUDE [register-provider](includes/register-provider.md)]
+[!INCLUDE [register-provider](./includes/register-provider.md)]
 
 [!INCLUDE [authorize-verified-partner-to-create-topic](includes/authorize-verified-partner-to-create-topic.md)]
 

articles/event-grid/blob-event-quickstart-portal.md

@@ -81,7 +81,7 @@ Before subscribing to the events for the Blob storage, let's create the endpoint
     > [!IMPORTANT]
     > Keep the Azure Event Grid Viewer window open so that you can see events as they are posted. 
 
-[!INCLUDE [event-grid-register-provider-portal.md](../../includes/event-grid-register-provider-portal.md)]
+[!INCLUDE [register-provider.md](./includes/register-provider.md)]
 
 ## Subscribe to the Blob storage