Fix title-case headings to sentence case across 19 guide pages

Author: brandonh6k

content/guides/angular/configure-github-actions.md

@@ -31,7 +31,7 @@ In this section, you'll set up a CI/CD pipeline using [GitHub Actions](https://d
 
 To enable GitHub Actions to build and push Docker images, you’ll securely store your Docker Hub credentials in your new GitHub repository.
 
-### Step 1: Generate Docker Hub Credentials and Set GitHub Secrets"
+### Step 1: Generate Docker Hub credentials and set GitHub secrets
 
 1. Create a Personal Access Token (PAT) from [Docker Hub](https://hub.docker.com)
    1. Go to your **Docker Hub account → Account Settings → Security**.

content/guides/angular/deploy.md

@@ -118,7 +118,7 @@ If everything is configured properly, you’ll see confirmation that both the De
 
 This confirms that both the Deployment and the Service were successfully created and are now running inside your local cluster.
 
-### Step 2. Check the Deployment status
+### Step 2. Check the deployment status
 
 Run the following command to check the status of your deployment:
 
@@ -135,7 +135,7 @@ You should see output similar to the following:
 
 This confirms that your pod is up and running with one replica available.
 
-### Step 3. Verify the Service exposure
+### Step 3. Verify the service exposure
 
 Check if the NodePort service is exposing your app to your local machine:
 

content/guides/angular/develop.md

@@ -24,7 +24,7 @@ You’ll learn how to:
 
 ---
 
-## Automatically update services (Development Mode)
+## Automatically update services (development mode)
 
 Use Compose Watch to automatically sync source file changes into your containerized development environment. This provides a seamless, efficient development experience without restarting or rebuilding containers manually.
 

content/guides/dex.md

@@ -27,7 +27,7 @@ The official [Docker image for Dex](https://hub.docker.com/r/dexidp/dex/) provid
 
 [Docker Compose](/compose/): Recommended for managing multi-container Docker applications.
 
-### Setting Up Dex with Docker
+### Setting up Dex with Docker
 
 Begin by creating a directory for your Dex project:
 

content/guides/frameworks/laravel/development-setup.md

@@ -210,7 +210,7 @@ CMD ["bash"]
 > [!NOTE]
 > If you prefer a **one-service-per-container** approach, simply omit the workspace container and run separate containers for each task. For example, you could use a dedicated `php-cli` container for your PHP scripts, and a `node` container to handle the asset building.
 
-## Create a Docker Compose Configuration for development
+## Create a Docker Compose configuration for development
 
 Here's the `compose.yaml` file to set up the development environment:
 

content/guides/nextjs/deploy.md

@@ -116,7 +116,7 @@ If everything is configured properly, you'll see confirmation that both the Depl
 
 This output means that both the Deployment and the Service were successfully created and are now running inside your local cluster.
 
-### Step 2. Check the Deployment status
+### Step 2. Check the deployment status
 
 Run the following command to check the status of your deployment:
 
@@ -133,7 +133,7 @@ You should see an output similar to:
 
 This confirms that your pod is up and running with one replica available.
 
-### Step 3. Verify the Service exposure
+### Step 3. Verify the service exposure
 
 Check if the NodePort service is exposing your app to your local machine:
 

content/guides/nextjs/develop.md

@@ -24,7 +24,7 @@ You'll learn how to:
 
 ---
 
-## Automatically update services (Development Mode)
+## Automatically update services (development mode)
 
 Use Compose Watch to automatically sync source file changes into your
 containerized development environment. This automatically syncs file changes

content/guides/nodejs/develop.md

@@ -354,7 +354,7 @@ $ npm run db:start    # Start PostgreSQL container
 $ npm run dev         # Start both server and client
 ```
 
-### Using Task Runner (alternative)
+### Using Task runner (alternative)
 
 The project includes a Taskfile.yml for advanced workflows:
 

content/guides/opentelemetry.md

@@ -33,7 +33,7 @@ The [Docker Official Image for OpenTelemetry](https://hub.docker.com/r/otel/open
 
 Basic knowledge of Node.js and Docker.
 
-## Project Structure
+## Project structure
 
 Create the project directory:
 ```bash
@@ -51,7 +51,7 @@ otel-js-app/
 │   └── tracer.js
 ```
 
-## Create a Simple Node.js App
+## Create a simple Node.js app
 
 Initialize a basic Node.js app:
 
@@ -82,7 +82,7 @@ app.listen(PORT, () => {
 });
 ```
 
-## Configure OpenTelemetry Tracing
+## Configure OpenTelemetry tracing
 
 Create the tracer configuration file:
 
@@ -128,7 +128,7 @@ service:
       exporters: [logging, jaeger]
 ```
 
-## Add Docker Compose Configuration
+## Add Docker Compose configuration
 
 Create the `docker-compose.yaml` file:
 
@@ -173,7 +173,7 @@ RUN npm install
 CMD ["node", "app.js"]
 ```
 
-## Start the Stack
+## Start the stack
 
 Start all services with Docker Compose:
 
@@ -187,7 +187,7 @@ Visit your app at [http://localhost:3000](http://localhost:3000)
 
 View traces at [http://localhost:16686](http://localhost:16686) in the Jaeger UI
 
-## Verify Traces in Jaeger
+## Verify traces in Jaeger
 
 After visiting your app's root endpoint, open Jaeger’s UI, search for the service (default is usually `unknown_service` unless explicitly named), and check the traces.
 

content/guides/postgresql/companions-for-postgresql.md

@@ -10,7 +10,7 @@ weight: 40
 ---
 
 
-## PostgreSQL Ecosystem companions: pgAdmin, PgBouncer, and Performance Testing
+## PostgreSQL ecosystem companions: pgAdmin, PgBouncer, and performance testing
 
 Running a standalone PostgreSQL container is often just the beginning. What happens when thousands of connections arrive, or when you need a visual interface to manage your database?