Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into fixEncHost

Author: roygara

articles/frontdoor/media/quickstart-create-front-door-cli/environment-diagram.png

@@ -7,7 +7,7 @@ manager: KumudD
 ms.service: frontdoor
 ms.topic: quickstart
 ms.workload: infrastructure-services
-ms.date: 4/19/2021
+ms.date: 3/28/2023
 ms.author: duau
 ms.custom: mode-api, devx-track-azurecli 
 ms.devlang: azurecli
@@ -18,9 +18,9 @@ ms.devlang: azurecli
 
 Get started with Azure Front Door by using Azure CLI to create a highly available and high-performance global web application.
 
-The Front Door directs web traffic to specific resources in a backend pool. You defined the frontend domain, add resources to a backend pool, and create a routing rule. This article uses a simple configuration of one backend pool with two web app resources and a single routing rule using default path matching "/*".
+The Front Door directs web traffic to specific resources in a backend pool. You defined the frontend domain, add resources to a backend pool, and create a routing rule. This article uses a simple configuration of one backend pool with a web app resource and a single routing rule using default path matching "/*".
 
-:::image type="content" source="media/quickstart-create-front-door/environment-diagram.png" alt-text="Diagram of Front Door deployment environment using the Azure CLI." border="false":::
+:::image type="content" source="media/quickstart-create-front-door-cli/environment-diagram.png" alt-text="Diagram of Front Door deployment environment using the Azure CLI." border="false":::
 
 ## Prerequisites
 
@@ -40,18 +40,14 @@ If you choose to install and use the CLI locally, this quickstart requires Azure
 
 In Azure, you allocate related resources to a resource group. You can either use an existing resource group or create a new one.
 
-For this quickstart, you need two resource groups. One in *Central US* and the second in *South Central US*.
+For this quickstart, you need a resource group in *Central US*.
 
 Create a resource group with [az group create](/cli/azure/group#az-group-create):
 
 ```azurecli-interactive
 az group create \
     --name myRGFDCentral \
     --location centralus
-
-az group create \
-    --name myRGFDEast \
-    --location eastus
 ```
 
 ## Create two instances of a web app
@@ -62,23 +58,19 @@ If you don't already have a web app, use the following script to set up two exam
 
 ### Create app service plans
 
-Before you can create the web apps you will need two app service plans, one in *Central US* and the second in *East US*.
+Before you can create the web app you will need an app service plan in *Central US*.
 
 Create app service plans with [az appservice plan create](/cli/azure/appservice/plan#az-appservice-plan-create&preserve-view=true):
 
 ```azurecli-interactive
 az appservice plan create \
 --name myAppServicePlanCentralUS \
 --resource-group myRGFDCentral
-
-az appservice plan create \
---name myAppServicePlanEastUS \
---resource-group myRGFDEast
 ```
 
 ### Create web apps
 
-Running the following commands will create a web app in each of the app service plans in the previous step. Web app names have to be globally unique.
+Running the following commands will create a web app in the app service plans in the previous step. Web app names have to be globally unique.
 
 Create web app with [az webapp create](/cli/azure/webapp#az-webapp-create&preserve-view=true):
 
@@ -87,14 +79,9 @@ az webapp create \
 --name WebAppContoso-1 \
 --resource-group myRGFDCentral \
 --plan myAppServicePlanCentralUS 
-
-az webapp create \
---name WebAppContoso-2 \
---resource-group myRGFDEast \
---plan myAppServicePlanEastUS
 ```
 
-Make note of the default host name of each web app so you can define the backend addresses when you deploy the Front Door in the next step.
+Make note of the default host name of the web app so you can define the backend addresses when you deploy the Front Door in the next step.
 
 ## Create the Front Door
 
@@ -107,7 +94,7 @@ az network front-door create \
 --resource-group myRGFDCentral \
 --name contoso-frontend \
 --accepted-protocols Http Https \
---backend-address webappcontoso-1.azurewebsites.net webappcontoso-2.azurewebsites.net 
+--backend-address webappcontoso-1.azurewebsites.net 
 ```
 
 **--resource-group:** Specify a resource group where you want to deploy the Front Door.
@@ -116,7 +103,7 @@ az network front-door create \
 
 **--accepted-protocols:** Accepted values are **Http** and **Https**. If you want to use both, specific both separated by a space.
 
-**--backend-address:** Define both web apps host name here separated by a space.
+**--backend-address:** Define the web app host name.
 
 Once the deployment has successfully completed, make note of the host name in the *frontEndpoints* section.
 
@@ -134,17 +121,14 @@ To delete the resource group use [az group delete](/cli/azure/group#az-group-del
 
 ```azurecli-interactive
 az group delete \
---name myRGFDCentral 
-
-az group delete \
---name myRGFDEast
+--name myRGFDCentral
 ```
 
 ## Next steps
 
 In this quickstart, you created a:
 * Front Door
-* Two web apps
+* A web app
 
 To learn how to add a custom domain to your Front Door, continue to the Front Door tutorials.
 

articles/frontdoor/quickstart-create-front-door-cli.md

@@ -35,7 +35,7 @@ To install the node exporter on Linux:
 
 1. The node exporter now starts collecting data. You can export the data at `http://IP:9100/metrics`.
 
-## Script to setup Node Exporter
+## Script to set up Node Exporter
 
 ```shell
 # To get the latest node exporter version from: https://prometheus.io/download/#node_exporter
@@ -52,7 +52,7 @@ else
 fi
 
 cd node_exporter-*.*-amd64
-nohup ./node_expoprter --web.listen-address=":9100" &
+nohup ./node_exporter --web.listen-address=":9100" &
 ```
 
 ## Prerequisites to enable secure communication
@@ -94,15 +94,15 @@ When the provider settings validation operation fails with the code ‘Prometheu
 1. Try to restart the node exporter agent:
     1. Go to the folder where you installed the node exporter (the file name resembles `node_exporter-*.*-amd64`).
     1. Run `./node_exporter`.
-    1. Adding nohup and & to aboe command decouples the node_exporter from linux machine commandline. If not included node_exporter would stop when the commandline is closed.
+    1. Adding nohup and & to above command decouples the node_exporter from linux machine commandline. If not included node_exporter would stop when the commandline is closed.
 1. Verify that the Prometheus endpoint is reachable from the subnet that you provided while creating the Azure Monitor for SAP solutions resource.
 
 ## Suggestions
 
 ### Enabling Node Exporter
 
 1. Run `nohup ./node_exporter &` command to enable node_exporter.
-1. Adding nohup and & to aboe command decouples the node_exporter from linux machine commandline. If not included node_exporter would stop when the commandline is closed.
+1. Adding nohup and & to above command decouples the node_exporter from linux machine commandline. If not included node_exporter would stop when the commandline is closed.
 
 ### Setting up cron job to start Node exporter on VM restart