docs: clarify that overrides are fully supported alongside overlays (#3333)

Co-authored-by: fern-support <support@buildwithfern.com>
Co-authored-by: Fern Support <info@buildwithfern.com>
Co-authored-by: Devin Logan <devinannlogan@gmail.com>

Author: 3 people

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

@@ -12,9 +12,9 @@ Overlays let you customize your OpenAPI specification without modifying the orig
 Overlays follow the [OpenAPI Overlay Specification](https://spec.openapis.org/overlay/v1.0.0.html).
 
 <Note>
-Overlays are the recommended approach for customizing OpenAPI specifications. Compared to [overrides](/api-definitions/overview/overrides), overlays offer additional capabilities like bulk modifications using JSONPath wildcards and the ability to modify elements within arrays. 
+  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 still supports overrides for backward compatibility.
+  [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).
 </Note>
 
 ## Configure overlays

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

@@ -11,7 +11,9 @@ Use an overrides file to customize your OpenAPI, AsyncAPI, or OpenRPC definition
 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.
 
 <Warning>
-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 still supports OpenAPI overrides for backward compatibility.
+  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.
+
+  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).
 </Warning>
 
 ## Implement overrides
@@ -102,4 +104,4 @@ paths:
 
 ## Overrides for different environments
 
-<Markdown src="/snippets/different-environments.mdx" type="overrides" />
+<Markdown src="/snippets/different-environments.mdx" type="overrides" />