chore: fix too-short meta descriptions for better seo (#2962)

Author: devalog

fern/products/api-def/asyncapi-pages/channels/pubsub.mdx

@@ -1,6 +1,6 @@
 ---
 title: Publish/Subscribe Operations
-subtitle: Document event-driven APIs with publish and subscribe operations
+description: Define AsyncAPI publish/subscribe operations for event-driven APIs. Step-by-step tutorial with message examples and bi-directional channels.
 ---
 
 Operations in AsyncAPI are defined underneath the `operations` key, with channels defined under the `channels` key. Below is an example of defining publish and subscribe operations: 

fern/products/api-def/asyncapi-pages/extensions/examples.mdx

@@ -1,6 +1,7 @@
 ---
 title: Request + response examples
-description: Provide additional examples for better SDK documentation using `x-fern-examples` extension
+description: Add message examples to AsyncAPI specs with `x-fern-examples`. Improve SDK documentation with real-world payload examples.
+og:title: AsyncAPI request + response examples
 ---
 
 Provide additional examples for better SDK documentation:

fern/products/api-def/asyncapi-pages/extensions/server-name.mdx

@@ -1,6 +1,6 @@
 ---
 title: Server names
-description: Specify custom names for servers using `x-fern-server-name` extension
+description: Configure custom server names in AsyncAPI specifications with `x-fern-server-name` extension. Set up production and staging server labels.
 ---
 
 Specify custom names for servers:

fern/products/api-def/ferndef-pages/auth.mdx

@@ -1,6 +1,6 @@
 ---
 title: Authentication
-subtitle: Model auth schemes such as bearer, basic, custom headers, and oauth. 
+description: Configure API authentication in Fern Definition. Set up bearer tokens, basic auth, custom headers, and OAuth for your API endpoints.
 ---
 
 Configuring authentication schemes happens in the `api.yml` file. All Fern-generated SDKs support both direct configuration and environment variables for authentication credentials.

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

@@ -1,6 +1,6 @@
 ---
 title: What is a Fern Definition? 
-description: "A Fern Definition is a set of YAML files that describe your API."
+description: Fern Definition is a YAML format for API specifications. Define your REST API endpoints, data models, and errors in one source of truth.
 ---
 
 A Fern Definition is a set of YAML files that are the single source of truth for your API. You check your Fern Definition into your repo,

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

@@ -1,6 +1,6 @@
 ---
 title: Sync your gRPC specification
-subtitle: Automatically sync your Protocol Buffer changes to keep SDKs and docs up to date
+description: Automate gRPC specification syncing with Fern. Set up GitHub Actions, CI/CD pipelines, and scheduled updates for Protocol Buffer files.
 ---
 
 Keeping your gRPC specifications in sync with your codebase is crucial for maintaining accurate SDKs and documentation. Fern provides several automation options to streamline this process.

fern/products/api-def/grpc-pages/reference/generators-reference.mdx

@@ -1,6 +1,6 @@
 ---
 title: gRPC generators.yml reference
-description: Reference for configuring gRPC specifications in your generators.yml file
+description: Complete gRPC generators.yml reference guide for Fern. Learn how to configure root, target, overrides, and local-generation settings.
 ---
 
 The `generators.yml` file serves two roles: it declares your gRPC specification location (in the `api.specs` section), and configures SDK generation (in the optional `groups` section). 

fern/products/api-def/openapi-pages/extensions/availability.mdx

@@ -1,6 +1,6 @@
 ---
 title: Availability
-description: Mark endpoint availability status using `x-fern-availability` extension
+description: Mark API endpoint availability in OpenAPI with `x-fern-availability`. Set beta, deprecated, stable, etc. statuses for endpoints and sections.
 ---
 
 The `x-fern-availability` extension is used to mark the availability of an endpoint within your OpenAPI definition. The availability information propagates into the generated Fern Docs website as visual tags. 

fern/products/api-def/openapi-pages/extensions/base-path.mdx

@@ -1,12 +1,11 @@
 ---
 title: Base path
-description: Configure base path prepended to endpoints using `x-fern-base-path` extension
+description: Configure base paths in OpenAPI with `x-fern-base-path`. Set up endpoint prefixes like /v1 for your API definitions with Fern.
 ---
-## Base path
 
-The `x-fern-base-path` extension is used to configure the base path prepended to every endpoint.
+Use the `x-fern-base-path` extension to configure the base path prepended to every endpoint.
 
-In the example below, we have configured the `/v1` base path so the full endpoint path is
+The example below configures the `/v1` base path so the full endpoint path is
 `https://api.example.com/v1/users`.
 
 ```yaml title="Set the base path in openapi.yml" {1}

fern/products/api-def/openapi-pages/extensions/enums.mdx

@@ -1,6 +1,6 @@
 ---
 title: Enum descriptions and names
-description: Add descriptions and custom names to enum values using `x-fern-enum` extension
+description: Add descriptions to OpenAPI enum values with `x-fern-enum` extension. Customize enum names for cleaner SDK code and better documentation.
 ---
 
 OpenAPI doesn't natively support adding descriptions to enum values. To do this in Fern you can use the `x-fern-enum`