[REng, Rules] Small updates

Author: pedrosousa

src/content/docs/rules/transform/response-header-modification/index.mdx

@@ -63,7 +63,7 @@ You can create a response header transform rule [in the dashboard](/rules/transf
 
 - Currently, there is a limited number of HTTP response headers that you cannot change. Cloudflare may remove restrictions for some of these HTTP response headers when presented with valid use cases. [Create a post in the community](https://community.cloudflare.com) for consideration.
 
-- Any response header modifications will also apply to Cloudflare error pages and [custom error pages](/rules/custom-errors/).
+- Response Header Transform Rules will also apply to the default Cloudflare error pages and [Custom Errors](/rules/custom-errors/).
 
 - Modifying `cache-control`, `CDN-Cache-Control`, or `Cloudflare-CDN-Cache-Control` headers will not change the way Cloudflare caches an object. Instead, you should create a [Cache Rule](/cache/how-to/cache-rules/).
 

src/content/docs/workers/configuration/versions-and-deployments/gradual-deployments.mdx

@@ -125,7 +125,7 @@ You can set the `Cloudflare-Workers-Version-Key` header both when making an exte
 
 You may want to extract a version key from certain properties of your request such as the URL, headers or cookies. You can configure a [Ruleset Engine](/ruleset-engine/) rule on your zone to do this. This allows you to specify version affinity based on these properties without having to modify the external client that makes the request.
 
-For example, if your worker serves video assets under the URI path `/assets/` and you wanted requests to each unique asset to be handled by a consistent version, you could define the following [request header modification](/rules/transform/request-header-modification/) rule:
+For example, if your worker serves video assets under the URI path `/assets/` and you wanted requests to each unique asset to be handled by a consistent version, you could define the following [request header transform rule](/rules/transform/request-header-modification/):
 
 <Example>
 

src/content/fields/index.yaml

@@ -1940,7 +1940,7 @@ entries:
 
       For a list of 1XXX errors, refer to [Troubleshooting Cloudflare 1XXX errors](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/).
 
-      **Note**: This field is only available in [HTTP response header modifications](/rules/transform/response-header-modification/) and [Custom Errors](/rules/custom-errors/).
+      **Note**: This field is only available in [Response Header Transform Rules](/rules/transform/response-header-modification/) and [Custom Errors](/rules/custom-errors/).
     example_value: |-
       1020
 
@@ -1967,4 +1967,4 @@ entries:
 
       You can use this field to customize the response for a specific type of error (for example, all 1XXX errors or all WAF block actions).
 
-      **Note**: This field is only available in [HTTP response header modifications](/rules/transform/response-header-modification/) and [Custom Errors](/rules/custom-errors/).
+      **Note**: This field is only available in [Response Header Transform Rules](/rules/transform/response-header-modification/) and [Custom Errors](/rules/custom-errors/).