small updates to various pages

Author: devalog

fern/products/api-def/pages/project-structure.mdx

@@ -4,24 +4,24 @@ description: Describes the Fern folder structure
 ---
 
 Configuring fern starts with the `fern` folder. The fern folder contains your API definitions,
-generators, and your CLI version.
+SDK generators, and your CLI version.
 
 ## Directory structure
 
-When you run `fern init` (for the Fern Definition) or `fern init --spec-type path/to/spec`, your fern folder will be initialized with the following files:
+When you run `fern init` (for the Fern Definition) or `fern init --spec-type path/to/spec` (for other specs), your fern folder is initialized with the following files:
 
 ```bash
 fern/
-  ├─ fern.config.json # Root-level configuration for entire Fern project
-  ├─ generators.yml # Defines what SDKs and docs to generate from your API
-  └─ spec-folder/ # definition, openapi, asyncapi, etc
+  ├─ fern.config.json # Root-level config for entire Fern project
+  ├─ generators.yml # Defines SDKs and docs to generate
+  └─ spec-folder/ # definition, openapi, asyncapi, etc.
     └─ spec-file.yml # API specification file
 ```
 
 <Info>
   For Fern Definition, your API configuration is split across two files: `api.yml` for API-wide configuration and separate `.yml` files for your actual endpoint and type definitions. See [What is a Fern Definition?](/api-definitions/ferndef/overview) for more information. 
 
-  For other specification formats (OpenAPI, AsyncAPI), you'll have a single self-contained specification file. 
+  For the other specification formats ([OpenAPI](/api-definitions/openapi/overview), [AsyncAPI](/api-definitions/asyncapi/overview), [OpenRPC](/api-definitions/openrpc/overview), and [gRPC](/api-definitions/grpc/overview)), you'll have a single self-contained specification file. 
 </Info>
 
 <AccordionGroup>
@@ -55,12 +55,12 @@ api:
 
 The fern folder can house multiple API definitions. When you have multiple APIs, nest your definition files within an `apis` folder. 
 
-Each API must also have a separate `generators.yml` file that specifies the location of the API definition and contains information about that API's SDKs.
+Each API must also have a separate `generators.yml` file that specifies the location of the API definition and configures SDK generation.
 
 ```bash
 fern/
   ├─ fern.config.json
-  ├─ generators.yml # Optional: contains top-level configuration for all APIs
+  ├─ generators.yml # Optional: top-level configuration for all APIs
   └─ apis/
     └─ first-api/ # First API
         ├─ generators.yml # Required: points to API spec

fern/products/api-def/pages/what-is-an-api-definition.mdx

@@ -322,9 +322,9 @@ Fern integrates with several API definition formats:
 
 ## Why create an API definition? 
 
-Once you have an API definition, Fern will use it as an input to generate artifacts 
+Once you have an API definition, Fern uses it as an input to generate artifacts 
 like SDKs and API Reference documentation. Every time you update the API definition,
-you can regenerate these artifacts and ensure they are always up-to-date.
+you can regenerate these artifacts to ensure they are always up-to-date.
 
 <CardGroup cols={2}>
   <Card