Fix typo

Author: johndowns

articles/frontdoor/front-door-caching.md

@@ -96,7 +96,7 @@ If the origin uses Chunked Transfer Encoding (CTE) to send compressed data to th
 ::: zone-end
 
 > [!NOTE]
-> Range requests may be compressed into different sizes. Azure Front Door requires the content-length values to be the same for any GET HTTP request. If clients send byte range requests with the `Accept-Encoding` header that leads to the Origin responding with different content lengths, then Azure Front Door will return a 503 error. You can either disable compression on the origin, or create a Rules Engine rule to remove tge `Accept-Encoding` header from the request for byte range requests.
+> Range requests may be compressed into different sizes. Azure Front Door requires the content-length values to be the same for any GET HTTP request. If clients send byte range requests with the `Accept-Encoding` header that leads to the Origin responding with different content lengths, then Azure Front Door will return a 503 error. You can either disable compression on the origin, or create a Rules Engine rule to remove the `Accept-Encoding` header from the request for byte range requests.
 
 ## Query string behavior