Fix CI/CD and GitHub Actions casing, add Vale exceptions

- Restore proper casing for 'GitHub Actions' (not 'GitHub actions')
- Restore proper casing for 'CI/CD' (not 'Ci/cd')
- Restore proper casing for 'CircleCI' (not 'Circleci')
- Restore proper casing for 'GitLab CI' (not 'GitLab ci')
- Add exceptions to Vale Headings.yml for: GitHub, Actions, CI/CD, CircleCI, GitLab

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

Author: devin-ai-integration[bot]

.vale/styles/FernStyles/Headings.yml

@@ -27,3 +27,8 @@ exceptions:
   - Support
   - Markdown
   - Docs
+  - GitHub
+  - Actions
+  - CI/CD
+  - CircleCI
+  - GitLab

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

@@ -5,7 +5,7 @@ subtitle: Automatically sync your AsyncAPI spec changes to keep SDKs and docs up
 
 Keeping your AsyncAPI specifications in sync with your codebase is crucial for maintaining accurate SDKs and documentation. Fern provides several automation options to streamline this process.
 
-## GitHub actions
+## GitHub Actions
 
 Use Fern's GitHub Action to automatically update SDKs and docs when your AsyncAPI spec changes:
 
@@ -99,9 +99,9 @@ api:
       version: 0.8.8
 ```
 
-## Ci/cd integration
+## CI/CD integration
 
-### Circleci
+### CircleCI
 ```yaml title=".circleci/config.yml" {15-23}
 version: 2.1
 
@@ -126,7 +126,7 @@ workflows:
             - fern-context
 ```
 
-### GitLab ci
+### GitLab CI
 ```yaml title=".gitlab-ci.yml" {13-20}
 stages:
   - build
@@ -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/grpc-pages/automation.mdx

@@ -5,7 +5,7 @@ subtitle: Automatically sync your Protocol Buffer changes to keep SDKs and docs
 
 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.
 
-## GitHub actions
+## GitHub Actions
 
 Use Fern's GitHub Action to automatically update SDKs and docs when your Protocol Buffer files change:
 
@@ -128,9 +128,9 @@ api:
       version: 0.8.8
 ```
 
-## Ci/cd integration
+## CI/CD integration
 
-### Circleci
+### CircleCI
 ```yaml title=".circleci/config.yml" {15-26}
 version: 2.1
 
@@ -170,7 +170,7 @@ jobs:
             find proto -name "*.proto" -exec protoc --proto_path=proto --descriptor_set_out=/dev/null {} \;
 ```
 
-### GitLab ci
+### GitLab CI
 ```yaml title=".gitlab-ci.yml" {13-25}
 stages:
   - build

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

@@ -5,7 +5,7 @@ subtitle: Automatically sync your OpenRPC spec changes to keep SDKs and docs up
 
 Keeping your OpenRPC specifications in sync with your codebase is crucial for maintaining accurate SDKs and documentation. Fern provides several automation options to streamline this process.
 
-## GitHub actions
+## GitHub Actions
 
 Use Fern's GitHub Action to automatically update SDKs and docs when your OpenRPC spec changes:
 
@@ -99,9 +99,9 @@ api:
       version: 0.8.8
 ```
 
-## Ci/cd integration
+## CI/CD integration
 
-### Circleci
+### CircleCI
 ```yaml title=".circleci/config.yml" {15-23}
 version: 2.1
 
@@ -126,7 +126,7 @@ workflows:
             - fern-context
 ```
 
-### GitLab ci
+### GitLab CI
 ```yaml title=".gitlab-ci.yml" {13-20}
 stages:
   - build

fern/products/docs/pages/getting-started/pr-preview.mdx

@@ -23,9 +23,9 @@ fern generate --docs --preview
 └─
 ```
 
-## Usage in GitHub actions
+## Usage in GitHub Actions
 
-The following is a GitHub Action workflow that generates a preview URL for every pull request. [Be sure to add the `FERN_TOKEN` for your organization to the repository](/learn/cli-api/cli-reference/commands#fern-token). 
+The following is a GitHub Action workflow that generates a preview URL for every pull request. [Be sure to add the `FERN_TOKEN` for your organization to the repository](/learn/cli-api/cli-reference/commands#fern-token).
 
 <CodeBlock title = ".github/workflows/preview-docs.yml">
 ```yaml

fern/products/docs/pages/getting-started/publishing-your-docs.mdx

@@ -26,8 +26,8 @@ fern generate --docs
 └─
 ```
 
-### Usage in GitHub actions
-To automate the publishing process, you can use a GitHub Action workflow to publish your docs when a push is made to the `main` branch. [Be sure to add the `FERN_TOKEN` for your organization to the repository](/learn/cli-api/cli-reference/commands#fern-token). 
+### Usage in GitHub Actions
+To automate the publishing process, you can use a GitHub Action workflow to publish your docs when a push is made to the `main` branch. [Be sure to add the `FERN_TOKEN` for your organization to the repository](/learn/cli-api/cli-reference/commands#fern-token).
 
 ```yaml .github/workflows/publish-docs.yml
 name: Publish Docs
@@ -80,4 +80,4 @@ navigation: []
 
 Publish the updated configuration by running `fern generate --docs`. This will remove all content from your site, and users visiting any page will see a 404 error.
 </Step>
-</Steps>
+</Steps>