remove grpc references from overrides page

Author: devalog

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

@@ -3,12 +3,12 @@ title: Overrides
 description: Customize your API definition using a separate overrides file.
 ---
 
-Use an overrides file to customize your OpenAPI, AsyncAPI, OpenRPC, or gRPC definition without modifying the original spec. This is useful when:
+Use an overrides file to customize your OpenAPI, AsyncAPI, or OpenRPC definition without modifying the original spec. This is useful when:
 
 * Your API specification is auto-generated from server code
 * You need different configurations for SDKs versus documentation
 
-Overrides are available for OpenAPI, AsyncAPI, OpenRPC, and gRPC 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 are not needed for [Fern Definition](/api-definitions/ferndef/overview) since you can directly edit those files.
 
 <Note>
 While you can also embed [Fern extensions](/api-definitions/overview/overrides#definition-specific-extensions) directly in your API specification, using overrides files is the recommended approach as it keeps your original spec clean and separates concerns.
@@ -35,7 +35,7 @@ fern/
 </Step>
 <Step title="Customize your spec with Fern extensions">
 
-For OpenAPI, AsyncAPI, and OpenRPC, and gRPC, you can use [Fern's extensions](/api-definitions/overview/overrides#definition-specific-extensions) to apply customizations. 
+For OpenAPI, AsyncAPI, and OpenRPC, you can use [Fern's extensions](/api-definitions/overview/overrides#definition-specific-extensions) to apply customizations. 
 
 ```yml title="overrides.yml" {4-5}
 paths: