docs(api def): small updates to overlays page (#3491)

Author: devalog

fern/products/api-def/openapi-pages/overlays.mdx

@@ -8,13 +8,14 @@ Overlays let you customize your OpenAPI specification without modifying the orig
 - Your API specification is auto-generated from server code
 - You need different configurations for SDKs versus documentation
 - You want to add Fern configurations like pagination or SDK method names
+- You want to make bulk changes across many endpoints using JSONPath wildcards
 
-Overlays follow the [OpenAPI Overlay Specification](https://spec.openapis.org/overlay/v1.0.0.html).
+Overlays follow the [OpenAPI Overlay Specification](https://spec.openapis.org/overlay/v1.0.0.html) and are portable across the OpenAPI ecosystem.
 
 <Note>
-  Fern recommends using [OpenAPI overlays](/api-definitions/openapi/overlays) instead of overrides for OpenAPI specs. Overlays follow the official [OpenAPI Overlay Specification](https://spec.openapis.org/overlay/v1.0.0.html) and are portable across different tools.
+  Fern recommends using overlays instead of overrides for OpenAPI specs. 
 
-  [Overrides](/api-definitions/overview/overrides) are also fully supported. If your team already uses overrides, there's no need to switch unless you need advanced functionality. You can also use both together (overrides are applied first, then overlays).
+  [Overrides](/api-definitions/overview/overrides) are also fully supported. If overrides are working for your team, there's no need to switch. You can also use both together (overrides are applied first, then overlays).
 </Note>
 
 ## Configure overlays

fern/products/api-def/pages/overrides.mdx

@@ -8,12 +8,12 @@ Use an overrides file to customize your OpenAPI, AsyncAPI, or OpenRPC definition
 * Your API specification is auto-generated from server code
 * You need different configurations for SDKs versus documentation
 
-Overrides are available for OpenAPI, AsyncAPI, and OpenRPC specifications. They are not needed for [Fern Definition](/api-definitions/ferndef/overview) since you can directly edit those files.
+Overrides are available for OpenAPI, AsyncAPI, and OpenRPC specifications. They're not needed for [Fern Definition](/api-definitions/ferndef/overview) since you can directly edit those files.
 
 <Warning>
-  For OpenAPI specs, Fern recommends using [overlays](/learn/api-definitions/openapi/overlays) instead of overrides. Overlays follow the official [OpenAPI Overlay Specification](https://spec.openapis.org/overlay/v1.0.0.html) and are portable across different tools.
+  For OpenAPI specs, Fern recommends using [overlays](/learn/api-definitions/openapi/overlays) instead of overrides. Overlays follow the official [OpenAPI Overlay Specification](https://spec.openapis.org/overlay/v1.0.0.html), support bulk changes with JSONPath wildcards, and are portable across the OpenAPI ecosystem.
 
-  However, overrides are also fully supported. If your team already uses overrides, there's no need to switch unless you need advanced functionality. You can also use both together (overrides are applied first, then overlays).
+  Overrides are also fully supported. If overrides are working for your team, there's no need to switch. You can also use both together (overrides are applied first, then overlays).
 </Warning>
 
 ## Implement overrides