`d

Author: kamilkisiela

packages/web/docs/src/content/router/configuration/expressions.mdx

@@ -69,17 +69,17 @@ These values allow you to branch logic based on who is calling your API and what
 ### `.response`
 
 Available only in **response** header rules. It represents the HTTP response from a subgraph call.
-You can inspect `.response.status_code` or `.response.headers` and then set or override additional
-headers. For example, you could conditionally add a cache header based on the subgraph’s status
-code. This variable is not present when computing request headers or dynamic URLs, because the
-response does not yet exist.
+You can inspect `.response.url` or `.response.headers` and then set or override additional headers.
+For example, you could conditionally add a cache header based on the subgraph’s status code. This
+variable is not present when computing request headers or dynamic URLs, because the response does
+not yet exist.
 
 - `.response.headers` - a case‑insensitive map of response headers.
 
 ### `.subgraph`
 
-Available in both **request** and \*_response_& header rules. It provides metadata about the
-subgraph handling the current request, including:
+Available in both **request** and **response** header rules. It provides metadata about the subgraph
+handling the current request, including:
 
 - `.subgraph.name` - the name of the subgraph as defined in your supergraph schema.
 

packages/web/docs/src/content/router/configuration/override_subgraph_urls.mdx

@@ -54,7 +54,7 @@ When an `object` is provided, it must contain an `expression` that returns a URL
 [expression](./expressions) is evaluated for each request, allowing for request-time routing
 decisions.
 
-- `expression`: **(string, required)** A [expression](./expressions) that computes the new URL.
+- `expression`: **(string, required)** An [expression](./expressions) that computes the new URL.
 
 Within the `expression`, you have access to two key variables: