diff --git a/src/content/docs/cache/how-to/configure-cache-status-code.mdx b/src/content/docs/cache/how-to/configure-cache-status-code.mdx
index c80fde5a5349bf1..190551d6350d5de 100644
--- a/src/content/docs/cache/how-to/configure-cache-status-code.mdx
+++ b/src/content/docs/cache/how-to/configure-cache-status-code.mdx
@@ -4,7 +4,7 @@ pcx_content_type: how-to
 
 ---
 
-Enterprise customers can set cache time-to-live (TTL) based on the response status from the origin web server. Cache TTL refers to the duration of a resource in the Cloudflare network before being marked as `STALE` or discarded from cache. Status codes are returned by a resource’s origin.
+Customers can set cache time-to-live (TTL) based on the response status from the origin web server. Cache TTL refers to the duration of a resource in the Cloudflare network before being marked as `STALE` or discarded from cache. Status codes are returned by a resource's origin.
 
 Setting cache TTL based on response status overrides the [default cache behavior (standard caching)](/cache/concepts/default-cache-behavior/) for static files and overrides cache instructions sent by the origin web server. To cache non-static assets, set a [Cache Level of Cache Everything using a Cache Rule](/cache/how-to/cache-rules/create-api/#example-requests). Setting `no-store` **Cache-Control** or a low TTL (using `max-age`/`s-maxage`) increases requests to origin web servers and decreases performance.