guardrails docs updated v2

Author: siddharthsambharia-portkey

product/ai-gateway/cache-simple-and-semantic.mdx

@@ -18,6 +18,10 @@ Portkey cache serves requests upto **20x times faster** and **cheaper**.
 
 To enable Portkey cache, just add the `cache` params to your [config object](/api-reference/config-object#cache-object-details).
 
+<Note>
+    Caching will not work if the `x-portkey-debug: "false"` header is included in the request
+</Note>
+
 ## Simple Cache
 
 

product/guardrails.mdx

@@ -388,6 +388,9 @@ Each section contains an array of guardrail execution results, structured as fol
       <ResponseField name="log" type="string|null">
         Additional logging information (if available)
       </ResponseField>
+      <ResponseField name="error" type="string|object">
+        Error message or object if the guardrail encountered an error
+      </ResponseField>
     </Expandable>
   </ResponseField>
   <ResponseField name="feedback" type="object">
@@ -419,9 +422,6 @@ Each section contains an array of guardrail execution results, structured as fol
   <ResponseField name="async" type="boolean">
     Whether the guardrail was run asynchronously
   </ResponseField>
-  <ResponseField name="error" type="string|object">
-    Error message or object if the guardrail encountered an error
-  </ResponseField>
   <ResponseField name="type" type="string">
     Always "guardrail" for guardrail hooks
   </ResponseField>
@@ -497,7 +497,7 @@ Here's a simplified example of what the `hook_results` might look like in a resp
         },
         {
             "verdict": true,
-            "id": "character_check_guardrail",
+            "id": "character_check_guardrai",
             "transformed": false,
             "checks": [
                 {
@@ -594,7 +594,7 @@ Here's a simplified example of what the `hook_results` might look like in a resp
 }
 }
 ```
-This example corresponds to a confgi like:
+This example corresponds to a `config` like:
 ```json
 {
   "input_guardrails": [