updated for acrolinx.

Author: AbdullahBell

articles/cdn/cdn-dynamic-site-acceleration.md

@@ -97,6 +97,6 @@ To access the rules engine:
 
     ![Rules engine for DSA](./media/cdn-dynamic-site-acceleration/cdn-dsa-rules-engine.png)
 
-Alternatively, you can use two content delivery network endpoints: one endpoint optimized with DSA to deliver dynamic assets and another endpoint optimized with a static optimization type, such as general web delivery, to delivery cacheable assets. Modify your webpage URLs to link directly to the asset on the content delivery network endpoint you plan to use.
+Alternatively, you can use two content delivery network endpoints: one endpoint optimized with DSA to deliver dynamic assets and another endpoint optimized with a static optimization type, such as general web delivery, to deliver cacheable assets. Modify your webpage URLs to link directly to the asset on the content delivery network endpoint you plan to use.
 
 For example, `mydynamic.azureedge.net/index.html` is a dynamic page and is loaded from the DSA endpoint. The HTML page references multiple static assets such as JavaScript libraries or images that are loaded from the static content delivery network endpoint, such as `mystatic.azureedge.net/banner.jpg` and `mystatic.azureedge.net/scripts.js`.

articles/cdn/cdn-purge-endpoint.md

@@ -46,7 +46,7 @@ This guide walks you through purging assets from all edge nodes of an endpoint.
 	3. **Root domain purge**: Purge the root of the endpoint with "/" in the path.
 
    > [!TIP]
-   > 1. Paths must be specified for purge and must be a relative URL that fit the following [RFC 3986 - Uniform Resource Identifier (URI): Generic Syntax](https://datatracker.ietf.org/doc/html/rfc3986#section-3.3).
+   > 1. Paths must be specified for purge and must be a relative URL that fits the following [RFC 3986 - Uniform Resource Identifier (URI): Generic Syntax](https://datatracker.ietf.org/doc/html/rfc3986#section-3.3).
    >
    > 1. In Azure CDN from Microsoft, query strings in the purge URL path are not considered. If the path to purge is provided as `/TestCDN?myname=max`, only `/TestCDN` is considered. The query string `myname=max` is omitted. Both `TestCDN?myname=max` and `TestCDN?myname=clark` will be purged.
 

articles/cdn/cdn-real-time-stats.md

@@ -27,7 +27,7 @@ The following graphs are available:
 
 ## Accessing real-time status
 
-1. In the [Azure Portal](https://portal.azure.com), browse to your CDN profile.
+1. In the [Azure portal](https://portal.azure.com), browse to your CDN profile.
 
 2. From the CDN profile blade, click the **Manage** button.
 

articles/cdn/monitoring-and-access-log.md

@@ -156,7 +156,7 @@ Azure CDN from Microsoft Service currently provides Raw logs. Raw logs provide i
 | ClientIp | The IP address of the client that made the request. If there was an X-Forwarded-For header in the request, then the Client IP is picked from the same. |
 | ClientPort | The IP port of the client that made the request. |
 | HttpMethod | HTTP method used by the request. |
-| HttpStatusCode | The HTTP status code returned from the proxy. If a request to the origin timeouts the value for HttpStatusCode is set to **0**.|
+| HttpStatusCode | The HTTP status code returned from the proxy. If a request to the origin timeouts, the value for HttpStatusCode is set to **0**.|
 | HttpStatusDetails | Resulting status on the request. Meaning of this string value can be found at a Status reference table. |
 | HttpVersion | Type of the request or connection. |
 | POP | Short name of the edge where the request landed. |