[fix] guide issues

Author: kristiyan-velkov

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

@@ -37,18 +37,18 @@ To enable GitHub Actions to build and push Docker images, you'll securely store
 
 ### Step 1: Connect your GitHub repository to Docker Hub
 
-1. Create a Personal Access Token (PAT) from [Docker Hub](https://hub.docker.com)
+1. Create a Personal Access Token (PAT) from [Docker Hub](https://hub.docker.com).
    1. Go to your **Docker Hub account → Account Settings → Security**.
    2. Generate a new Access Token with **Read/Write** permissions.
    3. Name it something like `docker-nodejs-sample`.
    4. Copy and save the token — you'll need it in Step 4.
 
-2. Create a repository in [Docker Hub](https://hub.docker.com/repositories/)
+2. Create a repository in [Docker Hub](https://hub.docker.com/repositories/).
    1. Go to your **Docker Hub account → Create a repository**.
    2. For the Repository Name, use something descriptive — for example: `nodejs-sample`.
    3. Once created, copy and save the repository name — you'll need it in Step 4.
 
-3. Create a new [GitHub repository](https://github.com/new) for your Node.js project
+3. Create a new [GitHub repository](https://github.com/new) for your Node.js project.
 
 4. Add Docker Hub credentials as GitHub repository secrets.
 

content/guides/nodejs/containerize.md

@@ -644,16 +644,16 @@ This Dockerfile implements several strategies to minimize the final image size:
 
 **Expected size reduction**: ~50% smaller than standard Node.js images
 
-### Step 3: Configure the .dockerignore file
+### Step 2: Configure the .dockerignore file
 
 The `.dockerignore` file tells Docker which files and folders to exclude when building the image.
 
 > [!NOTE]
 > This helps:
 >
-> 1.Reduce image size  
-> 2.Speed up the build process  
-> 3.Prevent sensitive or unnecessary files (like `.env`, `.git`, or `node_modules`) from being added to the final image.
+> - Reduce image size  
+> - Speed up the build process  
+> - Prevent sensitive or unnecessary files (like `.env`, `.git`, or `node_modules`) from being added to the final image.
 >
 > To learn more, visit the [.dockerignore reference](/reference/dockerfile.md#dockerignore-file).
 
@@ -705,7 +705,7 @@ nodejs-sample-kubernetes.yaml
 !tsconfig.json
 ```
 
-### Step 4: Build the Node.js application image
+### Step 3: Build the Node.js application image
 
 After creating all the configuration files, your project directory should now contain all necessary Docker configuration files:
 
@@ -735,7 +735,7 @@ What this command does:
 - Packages the application and its dependencies into a Docker image
 - Tags the image as docker-nodejs-sample so you can reference it later
 
-#### Step 6: View local images
+#### Step 4: View local images
 
 After building your Docker image, you can check which images are available on your local machine using either the Docker CLI or [Docker Desktop](/manuals/desktop/use-desktop/images.md). Since you're already working in the terminal, let's use the Docker CLI.
 

content/guides/nodejs/develop.md

@@ -166,7 +166,7 @@ networks:
 
 1. The PostgreSQL database configuration is handled automatically by the application. The database is created and initialized when the application starts, with data persisted using the `postgres_data` volume.
 
-2. Configure your environment by copying the example file:
+1. Configure your environment by copying the example file:
 
    ```console
    $ cp .env.example .env
@@ -192,25 +192,25 @@ networks:
    ALLOWED_ORIGINS=http://localhost:3000,http://localhost:5173
    ```
 
-3. Run the following command to start your application in development mode:
+1. Run the following command to start your application in development mode:
 
    ```console
    $ docker compose up app-dev --build
    ```
 
-4. Open a browser and verify that the application is running at [http://localhost:5173](http://localhost:5173) for the frontend or [http://localhost:3000](http://localhost:3000) for the API. The React frontend is served by Vite dev server on port 5173, with API calls proxied to the Express server on port 3000.
+1. Open a browser and verify that the application is running at [http://localhost:5173](http://localhost:5173) for the frontend or [http://localhost:3000](http://localhost:3000) for the API. The React frontend is served by Vite dev server on port 5173, with API calls proxied to the Express server on port 3000.
 
-5. Add some items to the todo list to test data persistence.
+1. Add some items to the todo list to test data persistence.
 
-6. After adding some items to the todo list, press `CTRL + C` in the terminal to stop your application.
+1. After adding some items to the todo list, press `CTRL + C` in the terminal to stop your application.
 
-7. Run the application again:
+1. Run the application again:
 
-   ```console
-   $ docker compose up app-dev
-   ```
+  ```console
+  $ docker compose up app-dev
+  ```
 
-8. Refresh [http://localhost:5173](http://localhost:5173) in your browser and verify that the todo items persisted, even after the containers were removed and ran again.
+1. Refresh [http://localhost:5173](http://localhost:5173) in your browser and verify that the todo items persisted, even after the containers were removed and ran again.
 
 ## Configure and run a development container
 
@@ -355,7 +355,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 comprehensive Taskfile.yml for advanced workflows:
 
@@ -397,55 +397,55 @@ Any changes to the application's source files on your local machine will now be
 Try making a change to test hot reloading:
 
 1. Open `src/client/components/TodoApp.tsx` in an IDE or text editor
-2. Update the main heading text:
-
-```diff
-- <h1 className="text-3xl font-bold text-gray-900 mb-8">
--   Modern Todo App
-- </h1>
-+ <h1 className="text-3xl font-bold text-gray-900 mb-8">
-+   My Todo App
-+ </h1>
-```
+1. Update the main heading text:
+
+  ```diff
+    - <h1 className="text-3xl font-bold text-gray-900 mb-8">
+    -   Modern Todo App
+    - </h1>
+    + <h1 className="text-3xl font-bold text-gray-900 mb-8">
+    +   My Todo App
+    + </h1>
+  ```
 
 1. Save the file and the Vite dev server will automatically reload the page with your changes
 
-**Debugging Support:**
+**Debugging support:**
 
 You can connect a debugger to your application on port 9229. The Node.js inspector is enabled with `--inspect=0.0.0.0:9230` in the development script (`dev:server`).
 
-### VS Code Debugger Setup
+### VS Code debugger setup
 
-1. **Create a launch configuration** in `.vscode/launch.json`:
+1. Create a launch configuration in `.vscode/launch.json`:
 
-```json
-{
-  "version": "0.2.0",
-  "configurations": [
+  ```json
     {
-      "name": "Attach to Docker Container",
-      "type": "node",
-      "request": "attach",
-      "port": 9229,
-      "address": "localhost",
-      "localRoot": "${workspaceFolder}",
-      "remoteRoot": "/app",
-      "protocol": "inspector",
-      "restart": true,
-      "sourceMaps": true,
-      "skipFiles": ["<node_internals>/**"]
+      "version": "0.2.0",
+      "configurations": [
+        {
+          "name": "Attach to Docker Container",
+          "type": "node",
+          "request": "attach",
+          "port": 9229,
+          "address": "localhost",
+          "localRoot": "${workspaceFolder}",
+          "remoteRoot": "/app",
+          "protocol": "inspector",
+          "restart": true,
+          "sourceMaps": true,
+          "skipFiles": ["<node_internals>/**"]
+        }
+      ]
     }
-  ]
-}
 ```
 
-1. **Start your development container**:
+1. Start your development container:
 
-```console
-docker compose up app-dev --build
-```
+  ```console
+  docker compose up app-dev --build
+  ```
 
-1. **Attach the debugger**:
+1. Attach the debugger:
    - Open VS Code
    - Go to the Debug panel (Ctrl/Cmd + Shift + D)
    - Select "Attach to Docker Container" from the drop-down
@@ -455,27 +455,27 @@ docker compose up app-dev --build
 
 You can also use Chrome DevTools for debugging:
 
-1. **Start your container** (if not already running):
+1. Start your container (if not already running):
 
-```console
-docker compose up app-dev --build
-```
+  ```console
+    docker compose up app-dev --build
+  ```
 
-1. **Open Chrome** and navigate to:
+1. Open Chrome and navigate to:
 
-```text
-chrome://inspect
-```
+  ```text
+  chrome://inspect
+  ```
 
-1. **Select "Configure"** and add:
+1. Select **Configure** and add:
 
-```text
-localhost:9229
-```
+  ```text
+  localhost:9229
+  ```
 
-1. **Select "inspect"** under your Node.js target when it appears
+1. Select **inspect** under your Node.js target when it appears.
 
-### Debugging Configuration Details
+### Debugging configuration details
 
 The debugger configuration:
 
@@ -485,32 +485,32 @@ The debugger configuration:
 
 The debugger listens on all interfaces (`0.0.0.0`) inside the container on port 9230 and is accessible on port 9229 from your host machine.
 
-### Troubleshooting Debugger Connection
+### Troubleshooting debugger connection
 
 If the debugger doesn't connect:
 
-1. **Check if the container is running**:
+1. Check if the container is running:
 
-```console
-docker ps
-```
+  ```console
+  docker ps
+  ```
 
-1. **Check if the port is exposed**:
+1. Check if the port is exposed:
 
-```console
-docker port todoapp-dev
-```
+  ```console
+  docker port todoapp-dev
+  ```
 
-1. **Check container logs**:
+1. Check container logs:
 
-```console
-docker compose logs app-dev
-```
+  ```console
+  docker compose logs app-dev
+  ```
 
-You should see a message like:
+  You should see a message like:
 
-```text
-Debugger listening on ws://0.0.0.0:9230/...
+  ```text
+  Debugger listening on ws://0.0.0.0:9230/...
 ```
 
 Now you can set breakpoints in your TypeScript source files and debug your containerized Node.js application!

content/guides/nodejs/run-tests.md

@@ -122,7 +122,7 @@ You should see output like the following:
    Duration  1.98s (transform 456ms, setup 1.26s, collect 1.74s, tests 1.87s, environment 5.82s, prepare 916ms)
 ```
 
-### Test Structure
+### Test structure
 
 The test suite covers: