Merge pull request #124984 from ArieHein/Spelling-Wave-4

Jak-MS · web-flow · commit fb25aedd7c74 · 2024-12-02T17:02:12.000-06:00
Spelling Fixes - Wave 4
diff --git a/articles/application-gateway/application-gateway-private-deployment.md b/articles/application-gateway/application-gateway-private-deployment.md
@@ -335,7 +335,7 @@ To create a route table and associate it to the Application Gateway subnet:
 
 2.	Select **Routes** and create the next hop rule for 0.0.0.0/0 and configure the destination to be the IP address of your VM:
 
- [ ![Screenshot of adding default route to network virtual applicance.](./media/application-gateway-private-deployment/default-route-nva.png) ](./media/application-gateway-private-deployment/default-route-nva.png#lightbox)
+ [ ![Screenshot of adding default route to network virtual appliance.](./media/application-gateway-private-deployment/default-route-nva.png) ](./media/application-gateway-private-deployment/default-route-nva.png#lightbox)
 
 3. Select **Subnets** and associate the route table to the Application Gateway subnet:
 
diff --git a/articles/application-gateway/application-gateway-troubleshooting-502.md b/articles/application-gateway/application-gateway-troubleshooting-502.md
@@ -123,7 +123,7 @@ Validate that the Custom Health Probe is configured correctly, as shown in the p
 * Ensure that the probe is correctly specified as per the [guide](application-gateway-create-probe-ps.md).
 * If  the application gateway is configured for a single site, by default the Host name should be specified as `127.0.0.1`, unless otherwise configured in custom probe.
 * Ensure that a call to http://\<host\>:\<port\>\<path\> returns an HTTP result code of 200.
-* Ensure that Interval, Timeout, and UnhealtyThreshold are within the acceptable ranges.
+* Ensure that Interval, Timeout, and UnhealthyThreshold are within the acceptable ranges.
 * If using an HTTPS probe, make sure that the backend server doesn't require SNI by configuring a fallback certificate on the backend server itself.
 
 ## Request time-out
diff --git a/articles/application-gateway/configure-application-gateway-with-private-frontend-ip.md b/articles/application-gateway/configure-application-gateway-with-private-frontend-ip.md
@@ -15,7 +15,7 @@ ms.author: greglin
 Azure Application Gateway Standard v1 can be configured with an Internet-facing VIP or with an internal endpoint that isn't exposed to the Internet. An internal endpoint uses a private IP address for the frontend, which is also known as an *internal load balancer (ILB) endpoint*.
 
 > [!NOTE]
-> Application Gateway v1 is being retired. See the [v1 retiredment announcement](/azure/application-gateway/v1-retirement).<br>
+> Application Gateway v1 is being retired. See the [v1 retirement announcement](/azure/application-gateway/v1-retirement).<br>
 > To configure a v2 application gateway with a private frontend IP address, see [Private Application Gateway deployment](/azure/application-gateway/application-gateway-private-deployment).
 
 Configuring the gateway using a frontend private IP address is useful for internal line-of-business applications that aren't exposed to the Internet. It's also useful for services and tiers within a multi-tier application that are in a security boundary that isn't exposed to the Internet but:
diff --git a/articles/application-gateway/create-url-route-portal.md b/articles/application-gateway/create-url-route-portal.md
@@ -198,7 +198,7 @@ Review the settings on the **Review + create** tab, and then select **Create** t
 
 3. Change the URL to *http://&lt;ip-address&gt;:8080/images/test.htm*, replacing &lt;ip-address&gt; with the public IP address of **myAppGateway**, and you should see something like the following example:
 
-    ![Screenshow of test images URL in application gateway](./media/application-gateway-create-url-route-portal/application-gateway-iistest-images.png)
+    ![Screenshot of test images URL in application gateway](./media/application-gateway-create-url-route-portal/application-gateway-iistest-images.png)
 
    The listener on port 8080 routes this request to the *Images* backend pool.
 
diff --git a/articles/application-gateway/deploy-basic-portal.md b/articles/application-gateway/deploy-basic-portal.md
@@ -225,7 +225,7 @@ Use IIS to test the application gateway:
 2. Copy the public IP address, and then paste it into the address bar of your browser to browse that IP address.
 3. Check the response. A valid response verifies that the application gateway was successfully created and can successfully connect with the backend.
 
-   ![A screenshow displaying a successful test of the application gateway.](./media/application-gateway-create-gateway-portal/application-gateway-iistest.png)
+   ![A screenshot displaying a successful test of the application gateway.](./media/application-gateway-create-gateway-portal/application-gateway-iistest.png)
 
    Refresh the browser multiple times and you should see connections to both myVM and myVM2.
 
diff --git a/articles/application-gateway/for-containers/custom-health-probe.md b/articles/application-gateway/for-containers/custom-health-probe.md
@@ -29,7 +29,7 @@ The following properties make up custom health probes:
 | timeout | How long in seconds the request should wait until it's marked as a failure. The minimum interval must be > 0 seconds. |
 | healthyThreshold | Number of health probes before marking the target endpoint healthy. The minimum interval must be > 0. |
 | port | The port number used when probing the backend target. |
-| unhealthyTreshold | Number of health probes to fail before the backend target should be labeled unhealthy. The minimum interval must be > 0. |
+| unhealthyThreshold | Number of health probes to fail before the backend target should be labeled unhealthy. The minimum interval must be > 0. |
 | grpc | Specified if the backend service is expecting gRPC connections. The value must be `{}`. |
 | (http) | Specified if the backend service is expecting http connections. |
 | (http) host | The hostname specified in the request to the backend target. |
@@ -51,8 +51,8 @@ When the default health probe is used, the following values for each health prob
 | -------- | ------------- |
 | interval | 5 seconds |
 | timeout | 30 seconds |
-| healthyTrehshold | 1 probe |
-| unhealthyTreshold | 3 probes |
+| healthyThreshold | 1 probe |
+| unhealthyThreshold | 3 probes |
 | port | The port number used is defined by the backend port number in the Ingress resource or HttpRoute backend port in the HttpRoute resource. |
 | (http) host | localhost |
 | (http) path | / |
diff --git a/articles/application-gateway/for-containers/how-to-header-rewrite-gateway-api.md b/articles/application-gateway/for-containers/how-to-header-rewrite-gateway-api.md
@@ -172,7 +172,7 @@ In this example, we look for the user agent used by the Bing search engine and s
 This example also demonstrates addition of a new header called `AGC-Header-Add` with a value of `AGC-value` and removes a request header called `client-custom-header`.
 
 > [!TIP]
-> For this example, while we can use the HTTPHeaderMatch of "Exact" for a string match, a demonstration is used in regular expression for illistration of further capabilities.
+> For this example, while we can use the HTTPHeaderMatch of "Exact" for a string match, a demonstration is used in regular expression for illustration of further capabilities.
 
 ```bash
 kubectl apply -f - <<EOF
diff --git a/articles/application-gateway/for-containers/how-to-header-rewrite-ingress-api.md b/articles/application-gateway/for-containers/how-to-header-rewrite-ingress-api.md
@@ -173,7 +173,7 @@ In this example, we set a static user-agent with a value of `rewritten-user-agen
 This example also demonstrates addition of a new header called `AGC-Header-Add` with a value of `AGC-value` and removes a request header called `client-custom-header`.
 
 > [!TIP]
-> For this example, while we can use the HTTPHeaderMatch of "Exact" for a string match, a demonstration is used in regular expression for illistration of further capabilities.
+> For this example, while we can use the HTTPHeaderMatch of "Exact" for a string match, a demonstration is used in regular expression for illustration of further capabilities.
 
 ```bash
 kubectl apply -f - <<EOF
diff --git a/articles/application-gateway/for-containers/migrate-from-agic-to-agc.md b/articles/application-gateway/for-containers/migrate-from-agic-to-agc.md
@@ -329,7 +329,7 @@ Application Gateway for Containers implementation
 
 #### [Header rewrite in Gateway API](how-to-header-rewrite-ingress-api.md)
 
-In Gateway API, you define a RequestHeaderModifer match and filter to rewrite the request.
+In Gateway API, you define a RequestHeaderModifier match and filter to rewrite the request.
 
 #### [Header rewrite in Ingress API](how-to-header-rewrite-ingress-api.md)
 
diff --git a/articles/application-gateway/for-containers/prometheus-grafana.md b/articles/application-gateway/for-containers/prometheus-grafana.md
@@ -132,7 +132,7 @@ In this section, we enter Grafana default dashboards.
 
 4. After entering your user credentials, refer to the Grafana introduction.
 5. Select on the left side bar to access default dashboards under dashboards.
-   ![A screenshot of Dafault Grafana Dashboard.](./media/prometheus-grafana/grafana-default.png)
+   ![A screenshot of Default Grafana Dashboard.](./media/prometheus-grafana/grafana-default.png)
 
 ## Graph Prometheus metrics on Grafana 
 
diff --git a/articles/application-gateway/for-containers/tls-policy.md b/articles/application-gateway/for-containers/tls-policy.md
@@ -55,7 +55,7 @@ When no TLS Policy is specified within your Kubernetes configuration, **predefin
 
 # [Gateway API](#tab/tls-policy-gateway-api)
 
-TLS policy can be defined in a [FrontendTLSPolicy](api-specification-kubernetes.md#alb.networking.azure.io/v1.FrontendTLSPolicy) resource, which targets defined gateway listeners.  Specify a policyType of type `predefinned` and use choose either predefined policy name: `2023-06` or `2023-06-S`
+TLS policy can be defined in a [FrontendTLSPolicy](api-specification-kubernetes.md#alb.networking.azure.io/v1.FrontendTLSPolicy) resource, which targets defined gateway listeners.  Specify a policyType of type `predefined` and use choose either predefined policy name: `2023-06` or `2023-06-S`
 
 Example command to create a new FrontendTLSPolicy resource with the predefined TLS policy 2023-06-S.
 
diff --git a/articles/application-gateway/ingress-controller-troubleshoot.md b/articles/application-gateway/ingress-controller-troubleshoot.md
@@ -122,7 +122,7 @@ Application Gateway has the following configuration applied:
 Finally we can use the `cURL` command from within [Cloud Shell](https://shell.azure.com/) to establish an HTTP connection to the newly deployed app:
 
 1. Use `kubectl get ingress` to get the Public IP address of Application Gateway
-2. Use `curl -I -H 'test.agic.contoso.com' <publitc-ip-address-from-previous-command>`
+2. Use `curl -I -H 'test.agic.contoso.com' <public-ip-address-from-previous-command>`
 
 ![Screenshot of the Bash window in Azure Cloud Shell showing a cURL command successfully establishing an HTTP connection to the test app.](./media/application-gateway-ingress-controller-troubleshooting/tsg--curl.png)
 
@@ -282,7 +282,7 @@ appgw:
 # Specify which kubernetes namespace the ingress controller watches
 # Default value is "default"
 # Leaving this variable out or setting it to blank or empty string would
-# result in Ingress Controller observing all acessible namespaces.
+# result in Ingress Controller observing all accessible namespaces.
 #
 # kubernetes:
 #   watchNamespace: <namespace>
diff --git a/articles/application-gateway/redirect-external-site-cli.md b/articles/application-gateway/redirect-external-site-cli.md
@@ -83,7 +83,7 @@ It may take several minutes for the application gateway to be created. After the
 
 ### Add the redirection configuration
 
-Add the redirection configuration that sends traffic from *www\.consoto.org* to the listener for *www\.contoso.com* to the application gateway using [az network application-gateway redirect-config create](/cli/azure/network/application-gateway/redirect-config).
+Add the redirection configuration that sends traffic from *www\.contoso.org* to the listener for *www\.contoso.com* to the application gateway using [az network application-gateway redirect-config create](/cli/azure/network/application-gateway/redirect-config).
 
 ```azurecli-interactive
 az network application-gateway redirect-config create \
diff --git a/articles/application-gateway/redirect-internal-site-cli.md b/articles/application-gateway/redirect-internal-site-cli.md
@@ -115,7 +115,7 @@ az network application-gateway http-listener create \
 
 ### Add the redirection configuration
 
-Add the redirection configuration that sends traffic from *www\.consoto.org* to the listener for *www\.contoso.com* in the application gateway using [az network application-gateway redirect-config create](/cli/azure/network/application-gateway/redirect-config#az-network-application-gateway-redirect-config-create).
+Add the redirection configuration that sends traffic from *www\.contoso.org* to the listener for *www\.contoso.com* in the application gateway using [az network application-gateway redirect-config create](/cli/azure/network/application-gateway/redirect-config#az-network-application-gateway-redirect-config-create).
 
 ```azurecli-interactive
 az network application-gateway redirect-config create \
diff --git a/articles/application-gateway/resource-health-overview.md b/articles/application-gateway/resource-health-overview.md
@@ -52,7 +52,7 @@ If you're experiencing problems,  the **Unknown** health status might suggest th
 
 The **Degraded** health status indicates your gateway has detected a loss in performance, although it's still available for usage.
 
-![Degrated status](media/resource-health-overview/degraded.png)
+![Degraded status](media/resource-health-overview/degraded.png)
 
 ## Next steps
 
diff --git a/articles/application-gateway/rewrite-http-headers-url.md b/articles/application-gateway/rewrite-http-headers-url.md
@@ -183,7 +183,7 @@ Here are the steps for replacing the hostname:
 
 You can fix several security vulnerabilities by implementing necessary headers in the application response. These security headers include X-XSS-Protection, Strict-Transport-Security, and Content-Security-Policy. You can use Application Gateway to set these headers for all responses.
 
-![A screenshow of a security header.](./media/rewrite-http-headers-url/security-header.png)
+![A screenshot of a security header.](./media/rewrite-http-headers-url/security-header.png)
 
 ### Delete unwanted headers
 
@@ -197,7 +197,7 @@ It isn't possible to create a rewrite rule to delete the host header. If you att
 
 You can evaluate an HTTP request or response header for the presence of a header or server variable. This evaluation is useful when you want to perform a header rewrite only when a certain header is present.
 
-![A screenshow showing the check presence of a header action.](./media/rewrite-http-headers-url/check-presence.png)
+![A screenshot showing the check presence of a header action.](./media/rewrite-http-headers-url/check-presence.png)
 
 ## Common scenarios for URL rewrite
 
diff --git a/articles/application-gateway/ssl-certificate-management.md b/articles/application-gateway/ssl-certificate-management.md
@@ -17,7 +17,7 @@ Listener TLS/SSL certificates in Application Gateway are used for terminating cl
 
 The TLS/SSL certificates on application gateway are stored in local certificate objects or containers. This certificate container’s reference is then supplied to listeners to support TLS connections for clients. Refer to this illustration for better understanding.  
 
-![Diagram that shows how certficates are linked to a listener.](media/ssl-certificate-management/cert-reference.png)
+![Diagram that shows how certificates are linked to a listener.](media/ssl-certificate-management/cert-reference.png)
 
 Here is a sample application gateway configuration. The SSLCertificates property includes certificate object “contoso-agw-cert" linked to a key vault. The “listener1” references that certificate object.
 
@@ -27,7 +27,7 @@ Here is a sample application gateway configuration. The SSLCertificates property
 
 This section allows you to list all the SSL certificate objects that are present on your application gateway. This view is equivalent of running PowerShell command `Get-AzApplicationGatewaySslCertificate -ApplicationGateway $AppGW` or CLI command `az network application-gateway ssl-cert list --gateway-name --resource-group`. 
 
-![Diagram illustrates listener certficate management via portal.](media/ssl-certificate-management/listener-cert-list-view.png)
+![Diagram illustrates listener certificate management via portal.](media/ssl-certificate-management/listener-cert-list-view.png)
 
 This page gives you a quick summary of all the certificates, their types and association with listeners. 
 
