chore: fix heading to use title casing

Author: youngjungithub

website/docs/reference/openapi-generator/cli.md

@@ -2,15 +2,15 @@
 sidebar_position: 2
 ---
 
-# Command-line interface
+# Command-line Interface
 
 ## Overview
 
 The `openapi-generator` CLI tool converts your `@api-ts/io-ts-http` `apiSpec` definition
 into an OpenAPI 3.0 specification. When you run this tool, it reads a TypeScript file
 containing your API definition and outputs the OpenAPI specification to stdout.
 
-## Usage syntax
+## Usage Syntax
 
 ```shell
 openapi-generator [OPTIONS] [FLAGS] <file>

website/docs/reference/openapi-generator/configuration.md

@@ -12,7 +12,7 @@ You need to configure the generator to:
 - Define OpenAPI schemas for custom `io-ts` codecs that can't be automatically derived
   from the Abstract Syntax Tree (AST).
 
-## Preparing external types packages
+## Preparing External Types Packages
 
 To process `io-ts` types imported from other npm packages, ensure the following in the
 external package's `package.json`:
@@ -39,21 +39,21 @@ external package's `package.json`:
 2. Specify the source entry point using the `source` field (for example,
    `"source": "src/index.ts"`)
 
-## Defining custom codec schemas
+## Defining Custom Codec Schemas
 
 For custom `io-ts` codecs (such as those using `new t.Type(...)` or complex types not
 directly supported), you must define schemas manually using one of these methods:
 
-### Method 1: Via openapi-gen.config.js (recommended for type authors)
+### Method 1: Via `openapi-gen.config.js` (Recommended For Type Authors)
 
 You can define schemas directly within the package that declares the custom codecs:
 
 1. Create a file named `openapi-gen.config.js` in the root of the types package
 
 2. Update the package's `package.json` to include:
 
-- The `customCodecFile` field pointing to this file
-- The config file in the `files` array
+- The `customCodecFile` field pointing to this file.
+- The config file in the `files` array.
 
   ```json
   // package.json of the types package defining custom codecs
@@ -98,10 +98,10 @@ You can define schemas directly within the package that declares the custom code
 The exported function receives the `fp-ts/Either` namespace (`E`) as an argument. You
 should return an object where:
 
-- Keys are the exported names of your custom codecs
-- Values are functions that return `E.right()` with an OpenAPI schema object
+- Keys are the exported names of your custom codecs.
+- Values are functions that return `E.right()` with an OpenAPI schema object.
 
-### Method 2: Via --codec-file option (for consumers)
+### Method 2: Via `--codec-file` Option (For Consumers)
 
 You can define schemas in a configuration file within your project and pass the file
 path via the `--codec-file` option:
@@ -132,8 +132,8 @@ path via the `--codec-file` option:
 
 In this structure:
 
-- Keys of the top-level object are package names
-- Values are objects that map codec names to their schema definitions
+- Keys of the top-level object are package names.
+- Values are objects that map codec names to their schema definitions.
 
 3. Run the generator with the `--codec-file` option:
 

website/docs/reference/openapi-generator/index.md

@@ -2,15 +2,15 @@
 sidebar_position: 1
 ---
 
-# OpenAPI generator
+# OpenAPI Generator
 
 This section provides technical reference for the `@api-ts/openapi-generator`
 command-line utility. The documentation covers:
 
-- CLI usage and options
-- Configuration settings
-- Supported `io-ts` primitives
-- JSDoc annotation system
+- CLI usage and options.
+- Configuration settings.
+- Supported `io-ts` primitives.
+- JSDoc annotation system.
 
 You can use this reference to generate OpenAPI specifications from your
 `@api-ts/io-ts-http` API definitions.

website/docs/reference/openapi-generator/jsdoc.md

@@ -1,4 +1,4 @@
-# JSDoc annotations
+# JSDoc Annotations
 
 You can use JSDoc comments to enrich the generated OpenAPI specification. This reference
 describes the supported annotations for both endpoint definitions and schema
@@ -113,7 +113,7 @@ const GetUserRoute = h.httpRoute({
 });
 ```
 
-### Unknown tags
+### Unknown Tags
 
 The generator treats any JSDoc tag not listed above as an "unknown tag". It collects
 these tags into the `x-unknown-tags` object:
@@ -131,7 +131,7 @@ const GetUserRoute = h.httpRoute({
 In this example, `@version 2` becomes `{ "version": "2" }` and `@department Billing`
 becomes `{ "department": "Billing" }` in the `x-unknown-tags` object.
 
-## Schema annotations
+## Schema Annotations
 
 When you add JSDoc comments to `io-ts` type definitions or fields within `t.type`,
 `t.partial`, etc., they add detail to the corresponding OpenAPI schema object or
@@ -192,7 +192,7 @@ keywords:
 | `@private`    | `x-internal: true` | Marks schema/field as internal   |
 | `@deprecated` | `deprecated: true` | Marks schema/field as deprecated |
 
-## Example schema with annotations
+## Example Schema With Annotations
 
 ```typescript
 import * as t from 'io-ts';

website/docs/reference/openapi-generator/support.md

@@ -1,4 +1,4 @@
-# Supported io-ts primitives
+# Supported `io-ts` Primitives
 
 When you use the OpenAPI generator, it automatically derives schemas from the following
 `io-ts` primitives and combinators: