Fix sentence case in titles and headings

- Changed 'Parameter Names' to 'Parameter names' in AsyncAPI and OpenRPC parameter-names.mdx files
- Changed 'Specification' to 'specification' in all automation and overview page titles (AsyncAPI, OpenAPI, OpenRPC, gRPC)
- Changed 'Error Handling' to 'Error handling' in gRPC errors.mdx
- Changed 'Global Configuration' to 'Global configuration' in Fern Definition global-configuration.mdx
- Changed 'Binary Data and Files' to 'Binary data and files' in Fern Definition bytes.mdx
- Changed 'Multipart File Upload' to 'Multipart file upload' in Fern Definition and OpenAPI multipart.mdx files
- Changed 'Server-Sent Events and Streaming APIs' to 'Server-sent events and streaming APIs' in Fern Definition and OpenAPI sse.mdx files

Co-Authored-By: Devin Logan <[email protected]>

Author: devin-ai-integration[bot]

fern/products/api-def/asyncapi-pages/automation.mdx

@@ -1,5 +1,5 @@
 ---
-title: Sync your AsyncAPI Specification
+title: Sync your AsyncAPI specification
 subtitle: Automatically sync your AsyncAPI spec changes to keep SDKs and docs up to date
 ---
 
@@ -200,4 +200,4 @@ api:
       version: 0.8.8
 ```
 
-This ensures that any breaking changes to your AsyncAPI specification are detected and the appropriate team members are notified before the changes are propagated to your SDKs and documentation. 
+This ensures that any breaking changes to your AsyncAPI specification are detected and the appropriate team members are notified before the changes are propagated to your SDKs and documentation.  

fern/products/api-def/asyncapi-pages/extensions/parameter-names.mdx

@@ -1,5 +1,5 @@
 ---
-title: Parameter Names
+title: Parameter names
 subtitle: Use `x-fern-parameter-name` to customize SDK parameter names for message properties
 ---
 
@@ -76,4 +76,4 @@ channels:
           type: string
 ```
 
-This ensures consistent naming conventions across your SDK while maintaining compatibility with your existing message formats. 
+This ensures consistent naming conventions across your SDK while maintaining compatibility with your existing message formats.  

fern/products/api-def/asyncapi-pages/overview.mdx

@@ -1,5 +1,5 @@
 ---
-title: What is an AsyncAPI Specification?
+title: What is an AsyncAPI specification?
 description: AsyncAPI is a standard for documenting event-driven APIs
 ---
 
@@ -174,4 +174,4 @@ fern/
     └─ asyncapi.yml
 ```
 </Step>
-</Steps>
+</Steps>

fern/products/api-def/ferndef-pages/api-yml/global-configuration.mdx

@@ -1,5 +1,5 @@
 ---
-title: Global Configuration
+title: Global configuration
 description: Specify global headers, path parameters or query parameters meant to be included on every request.
 ---
 
@@ -52,4 +52,4 @@ service:
 ## Global query parameters
 
 You cannot yet specify query parameters that are meant to be included on every request.
-If you'd like to see this feature, please upvote [this issue](https://github.com/fern-api/fern/issues/2930).
+If you'd like to see this feature, please upvote [this issue](https://github.com/fern-api/fern/issues/2930).

fern/products/api-def/ferndef-pages/endpoints/bytes.mdx

@@ -1,5 +1,5 @@
 ---
-title: Binary Data and Files
+title: Binary data and files
 subtitle: Use the `bytes` type to handle binary data in your API
 ---
 

fern/products/api-def/ferndef-pages/endpoints/multipart.mdx

@@ -1,5 +1,5 @@
 ---
-title: Multipart File Upload
+title: Multipart file upload
 description: Document endpoints with the `multiform` content type.
 ---
 

fern/products/api-def/ferndef-pages/endpoints/sse.mdx

@@ -1,5 +1,5 @@
 ---
-title: Server-Sent Events and Streaming APIs
+title: Server-sent events and streaming APIs
 subtitle: Use the `response-stream` key to model streaming endpoints
 ---
 
@@ -97,4 +97,4 @@ types:
   ChatChunk:
     properties:
       text: string
-```
+```

fern/products/api-def/grpc-pages/automation.mdx

@@ -1,5 +1,5 @@
 ---
-title: Sync your gRPC Specification
+title: Sync your gRPC specification
 subtitle: Automatically sync your Protocol Buffer changes to keep SDKs and docs up to date
 ---
 
@@ -469,4 +469,4 @@ if __name__ == "__main__":
     sync_from_grpc_reflection("localhost:50051", "proto/")
 ```
 
-This ensures that any changes to your gRPC services are automatically reflected in your SDKs and documentation, maintaining consistency across your entire API ecosystem.    
+This ensures that any changes to your gRPC services are automatically reflected in your SDKs and documentation, maintaining consistency across your entire API ecosystem.        

fern/products/api-def/grpc-pages/services/errors.mdx

@@ -1,5 +1,5 @@
 ---
-title: Error Handling
+title: Error handling
 subtitle: Implement robust error handling with gRPC status codes and custom error details
 ---
 
@@ -523,4 +523,4 @@ message CreateUserResult {
 }
 ```
 
-Proper error handling in gRPC ensures robust, maintainable services that provide clear feedback to clients about what went wrong and how to fix it. 
+Proper error handling in gRPC ensures robust, maintainable services that provide clear feedback to clients about what went wrong and how to fix it.  

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

@@ -1,5 +1,5 @@
 ---
-title: Sync your OpenAPI Specification
+title: Sync your OpenAPI specification
 subtitle: Pull your latest OpenAPI Specification into your Fern Folder automatically.
 ---
 
@@ -59,4 +59,4 @@ This creates daily pull requests with any API spec updates. To change the freque
 
 ## Other use cases 
 
-If your OpenAPI spec lives in a different repository (rather than at a public URL), you can sync it to your Fern folder using explicit file mappings. See the [sync-openapi GitHub Action README](https://github.com/fern-api/sync-openapi) for this and other advanced configurations. 
+If your OpenAPI spec lives in a different repository (rather than at a public URL), you can sync it to your Fern folder using explicit file mappings. See the [sync-openapi GitHub Action README](https://github.com/fern-api/sync-openapi) for this and other advanced configurations.