updated for acrolinx.

Author: AbdullahBell

articles/frontdoor/how-to-configure-endpoints.md

@@ -49,11 +49,11 @@ Before you can create a new endpoint with Front Door manager, you must have an A
     | **Name** | Enter a unique name for the new route |
     | **Enable route** | Set as checked to enable this route. |
     | **Domains** | Select one or more validated domains that aren't associated to another route. For more information, see [add a custom domain](standard-premium/how-to-add-custom-domain.md). |
-    | **Patterns to match** | Configure all URL path patterns that this route accepts. For example, you can set the pattern to match to `/images/*` to accept all requests on the URL `www.contoso.com/images/*`. Azure Front Door determines the traffic based on exact match first. If no paths match exactly, then Front Door looks for a wildcard path that matches. If no routing rules are found with a matching path, then the request get rejected and returns a 400: Bad Request error HTTP response. Patterns to match paths aren't case sensitive, meaning paths with different casing are treated as duplicates. For example, you have a host using the same protocol with paths `/FOO` and `/foo`. These paths are considered duplicates, and aren't allowed in the *Patterns to match* field. |
+    | **Patterns to match** | Configure all URL path patterns that this route accepts. For example, you can set the pattern to match to `/images/*` to accept all requests on the URL `www.contoso.com/images/*`. Azure Front Door determines the traffic based on exact match first. If no paths match exactly, then Front Door looks for a wildcard path that matches. If no routing rules are found with a matching path, then the request gets rejected and returns a 400: Bad Request error HTTP response. Patterns to match paths aren't case sensitive, meaning paths with different casing are treated as duplicates. For example, you have a host using the same protocol with paths `/FOO` and `/foo`. These paths are considered duplicates, and aren't allowed in the *Patterns to match* field. |
     | **Accepted protocols** | Specify the protocols you want Azure Front Door to accept when the client is making the request. You can specify HTTP, HTTPS, or both. |
     | **Redirect** | Specify whether HTTPS is enforced for the incoming HTTP requests. |
     | **Origin group** | Select the origin group to forward traffic to when requests are made to the origin. For more information, see [configure an origin group](standard-premium/how-to-create-origin.md). |
-    | **Origin path** | This path is used to rewrite the URL that Front Door uses when forwarding the request to the origin. By default, this path isn't provided, so Front Door uses the incoming URL path in the request to the origin. You can also specify a wildcard path, which copies any matching part of the incoming path to the request path to the origin. Note that the origin path is case sensitive. |
+    | **Origin path** | This path is used to rewrite the URL that Front Door uses when forwarding the request to the origin. By default, this path isn't provided, so Front Door uses the incoming URL path in the request to the origin. You can also specify a wildcard path, which copies any matching part of the incoming path to the request path to the origin. The origin path is case sensitive. |
     | **Forwarding protocol** | Select the protocol used for forwarding request. You can specify HTTP only, HTTPS only, or match incoming request. |
     | **Caching** | Select this option to enable caching of static content with Azure Front Door. For more information, see [caching with Front Door](front-door-caching.md). |
     | **Rules** | Select rule sets that get applied to this route. For more information, see [rule sets for Front Door](front-door-rules-engine.md). |

articles/frontdoor/how-to-configure-origin.md

@@ -15,7 +15,7 @@ ms.author: duau
 This article shows you how to create an Azure Front Door origin in a new origin group. The origin group can be then associated with a route to determine how traffic reaches your origins.
 
 > [!NOTE]
-> An *Origin* and a *origin group* in this article refers to the backend and backend pool of the Azure Front Door (classic) configuration.
+> An *Origin* and an *origin group* in this article refers to the backend and backend pool of the Azure Front Door (classic) configuration.
 >
 
 ## Prerequisites