Updates

Author: johndowns

articles/frontdoor/front-door-caching.md

@@ -17,23 +17,23 @@ zone_pivot_groups: front-door-tiers
 
 In this article, you'll learn how Azure Front Door Standard and Premium tier routes and rule sets behave when you have caching enabled. Azure Front Door is a modern Content Delivery Network (CDN) with dynamic site acceleration and load balancing.
 
-## Caching architecture
+::: zone-end
 
-When caching is configured on your route, Front Door uses a multi-tier caching architecture. When a request is received, the edge site that receives the request checks its cache for a valid response. If none is available, it also checks a regional cache. This approach helps to reduce the amount of traffic sent to your origin server. If no cached response is available, the request is forwarded to the origin.
+::: zone pivot="front-door-classic"
 
-Each Front Door edge site manages its own cache, and requests might be served by different edge sites. As a result, you might still see some traffic reach your origin, even if you served cached responses.
+The following document specifies behaviors for Azure Front Door (classic) with routing rules that have enabled caching. Front Door is a modern Content Delivery Network (CDN) with dynamic site acceleration and load balancing, it also supports caching behaviors just like any other CDN.
 
-## Request methods
+::: zone-end
 
-Only requests that use the `GET` request method are cacheable. All other request methods are always proxied through the network.
+## Caching architecture
 
-::: zone-end
+When caching is configured on your route, the edge site that receives each request checks its cache for a valid response. Caching helps to reduce the amount of traffic sent to your origin server. If no cached response is available, the request is forwarded to the origin.
 
-::: zone pivot="front-door-classic"
+Each Front Door edge site manages its own cache, and requests might be served by different edge sites. As a result, you might still see some traffic reach your origin, even if you served cached responses.
 
-The following document specifies behaviors for Azure Front Door (classic) with routing rules that have enabled caching. Front Door is a modern Content Delivery Network (CDN) with dynamic site acceleration and load balancing, it also supports caching behaviors just like any other CDN.
+## Request methods
 
-::: zone-end
+Only requests that use the `GET` request method are cacheable. All other request methods are always proxied through the network.
 
 ## Delivery of large files
 
@@ -202,12 +202,19 @@ If the origin response is cacheable, then the `Set-Cookie` header is removed bef
 
 In addition, Front Door attaches the `X-Cache` header to all responses. The `X-Cache` response header includes one of the following values:
 
-- `TCP_HIT`: The first byte of the request is a cache hit in the Front Door edge. 
-- `TCP_REMOTE_HIT`: The first byte of the request is a cache hit in the regional cache (origin shield layer) but a miss in the edge cache. 
+- `TCP_HIT` or `TCP_REMOTE_HIT`: The first byte of the request is a cache hit, and content is served from the Front Door cache.
 - `TCP_MISS`: The first byte of the request is a cache miss, and the content is served from the origin.
 - `PRIVATE_NOSTORE`: Request can't be cached because the *Cache-Control* response header is set to either *private* or *no-store*.
 - `CONFIG_NOCACHE`: Request is configured to not cache in the Front Door profile.
 
+::: zone pivot="front-door-standard-premium"
+
+## Logs and reports
+
+The [Front Door Access Log](how-to-logs.md#access-log) includes the cache status for each request. Also, [reports](standard-premium/how-to-reports.md#caching) include information about how Front Door's cache is used in your application.
+
+::: zone-end
+
 ## Cache behavior and duration
 
 ::: zone pivot="front-door-standard-premium"

articles/frontdoor/standard-premium/how-to-logs.md

@@ -78,7 +78,7 @@ Azure Front Door currently provides individual API requests with each entry havi
 | Endpoint | The domain name of AFD endpoint, for example, contoso.z01.azurefd.net |
 | HttpStatusCode | The HTTP status code returned from Azure Front Door. If a request to the the origin timeout, the value for HttpStatusCode is set to **0**.|
 | Pop | The edge pop, which responded to the user request.  |
-| Cache Status | Provides the status code of how the request gets handled by the CDN service when it comes to caching. Possible values are HIT: The HTTP request was served from AFD edge POP cache. <br> **MISS**: The HTTP request was served from origin. <br/> **PARTIAL_HIT**: Some of the bytes from a request got served from AFD edge POP cache while some of the bytes got served from origin for object chunking scenarios. <br> **CACHE_NOCONFIG**: Forwarding requests without caching settings, including bypass scenario. <br/> **PRIVATE_NOSTORE**: No cache configured in caching settings by customers. <br> **REMOTE_HIT**: The request was served by parent node cache. <br/> **N/A**:** Request that was denied by Signed URL and Rules Set. |
+| Cache Status | Provides the status code of how the request gets handled by the CDN service when it comes to caching. Possible values are:<ul><li>`HIT` and `REMOTE_HIT`: The HTTP request was served from the Front Door cache.</ul><ul>`MISS`: The HTTP request was served from theorigin.</li><li> `PARTIAL_HIT`: Some of the bytes from a request were served from the Front Door cache, and some of the bytes were served from origin. This status occurs in [object chunking](../front-door-caching.md#delivery-of-large-files) scenarios.</li><li>`CACHE_NOCONFIG`: Request was forwarded without caching settings, including bypass scenario.</li><li>`PRIVATE_NOSTORE`: No cache configured in caching settings by customers.</li><li>`N/A`: The request was denied by a signed URL and rules engine. |
 | MatchedRulesSetName | The names of the rules that were processed. |
 | RouteName | The name of the route that the request matched. |
 | ClientPort | The IP port of the client that made the request. |

articles/frontdoor/standard-premium/how-to-reports.md

@@ -171,7 +171,7 @@ Cache Hits/Misses describe the request number cache hits and cache misses for cl
 
 This report takes caching scenarios into consideration and requests that met the following requirements are taken into calculation. 
 
-* The requested content was cached on the POP closest to the requester or origin shield. 
+* The requested content was cached on a Front Door PoP.
 
 * Partial cached contents for object chunking.