fix(es): review comments

Author: RoRoJ

pages/edge-services/troubleshooting/cache-problems.mdx

@@ -11,6 +11,10 @@ You may experience unexpected behavior with caching on your Edge Services pipeli
 
 This page helps you resolve common problems.
 
+<Message type="tip">
+Before diving into this troubleshooting guide, ensure you are correctly using `curl` for your testing. `curl -I` uses the HEAD method by default, which does not always trigger the same logic as a real `GET` request. This can mislead you during cache tests, as cache checks might be skipped entirely, and responses main contain different headers. Use `curl -X GET -I` for more better testing and accurate `X-Cache` header information in responses.
+</Message>
+
 ## Some assets are not being correctly cached by Edge Services.
 
 You may find that even though your application includes proper cache headers (e.g., `Cache-Control: max-age=...`) and is configured behind a Load Balancer with an Edge Services pipeline, static assets like images are not being cached. This can result in repeated `X-Cache: miss` responses,  occasional `502` errors, and a weak cache hit:miss ratio, despite the assets being successfully served. 
@@ -36,8 +40,8 @@ Check the X-Cache header in the response:
 - `X-Cache: hit-fresh`: the cache is working.  
 - `X-Cache: miss`: the cache was bypassed.
 
-<Message type="tip">
-Be cautious when using `curl` to test. `curl -I` uses the HEAD method by default, which can mislead you during troubleshooting. Use `curl -X GET -I` for more accurate testing.
-</Message>
+Use a cookie-free subdomain for static assets. This prevents cookies from being sent with requests for images, CSS, or JS.  
 
-Use a cookie-free subdomain for static assets. This prevents cookies from being sent with requests for images, CSS, or JS.  
+<Message type="important">
+If your cookies contain authentication data, be cautious when enabling caching with cookies. Without proper `Cache-Control` headers, sensitive content may be cached and exposed to other users. Evaluate security risks before overriding the default behavior.
+</Message>