[fix] minnor text issues and node.js image increase

Author: kristiyan-velkov

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

@@ -50,7 +50,7 @@ To enable GitHub Actions to build and push Docker images, you'll securely store
 
 3. Create a new [GitHub repository](https://github.com/new) for your Node.js project
 
-4. Add Docker Hub credentials as GitHub repository secrets
+4. Add Docker Hub credentials as GitHub repository secrets.
 
    In your newly created GitHub repository:
    1. Navigate to:
@@ -66,7 +66,7 @@ To enable GitHub Actions to build and push Docker images, you'll securely store
 
    These secrets let GitHub Actions to authenticate securely with Docker Hub during automated workflows.
 
-5. Connect Your Local Project to GitHub
+5. Connect your local project to GitHub.
 
    Link your local project `docker-nodejs-sample` to the GitHub repository you just created by running the following command from your project root:
 
@@ -92,7 +92,7 @@ To enable GitHub Actions to build and push Docker images, you'll securely store
 
    This confirms that your local repository is properly linked and ready to push your source code to GitHub.
 
-6. Push Your Source Code to GitHub
+6. Push your source code to GitHub.
 
    Follow these steps to commit and push your local project to your GitHub repository:
    1. Stage all files for commit.

content/guides/nodejs/containerize.md

@@ -1,5 +1,5 @@
 ---
-title: Containerize a Node.js Application
+title: Containerize a Node.js application
 linkTitle: Containerize
 weight: 10
 keywords: node.js, node, containerize, initialize
@@ -81,7 +81,7 @@ For consistency, use the same responses shown in the example following when prom
 | Question | Answer |
 |------------------------------------------------------------|-----------------|
 | What application platform does your project use? | Node |
-| What version of Node do you want to use? | 22.21.0-alpine3.21 |
+| What version of Node do you want to use? | 24.11.1-alpine |
 | Which package manager do you want to use? | npm |
 | Do you want to run "npm run build" before starting server? | yes |
 | What directory is your build output to? | dist |
@@ -297,9 +297,9 @@ ALLOWED_ORIGINS=http://localhost:3000,http://localhost:5173
 
 The default Dockerfile generated by `docker init` provides a reliable baseline for standard Node.js applications. However, since this project is a full-stack TypeScript application that includes both a backend API and frontend React components, the Dockerfile should be customized to better support and optimize this specific architecture.
 
-### Step 1: Review the generated files
+### Review the generated files
 
-In this step, you’ll improve the Dockerfile and configuration files by following best practices:
+In the following step, you’ll improve the Dockerfile and configuration files by following best practices:
 
 - Use multi-stage builds to keep the final image clean and small
 - Improve performance and security by only including what’s needed
@@ -310,25 +310,30 @@ These updates help ensure your app is easy to deploy, fast to load, and producti
 > A `Dockerfile` is a plain text file that contains step-by-step instructions to build a Docker image. It automates packaging your application along with its dependencies and runtime environment.  
 > For full details, see the [Dockerfile reference](/reference/dockerfile/).
 
-### Step 2: Configure the Dockerfile file
+### Step 1: Configure the Dockerfile
 
 Before creating a Dockerfile, you need to choose a base image. You can either use the [Node.js Official Image](https://hub.docker.com/_/node) or a Docker Hardened Image (DHI) from the [Hardened Image catalog](https://hub.docker.com/hardened-images/catalog).
 
 Choosing DHI offers the advantage of a production-ready image that is lightweight and secure. For more information, see [Docker Hardened Images](https://docs.docker.com/dhi/).
 
+> [!IMPORTANT]
+> This guide uses a stable Node.js LTS image tag that is considered secure when the guide is written. Because new releases and security patches are published regularly, the tag shown here may no longer be the safest option when you follow the guide. Always review the latest available image tags and select a secure, up-to-date version before building or deploying your application.
+>
+> Official Node.js Docker Images: https://hub.docker.com/_/node
+
 {{< tabs >}}
 {{< tab name="Using Docker Hardened Images" >}}
 Docker Hardened Images (DHIs) are available for Node.js on [Docker Hub](https://hub.docker.com/hardened-images/catalog/dhi/node). Unlike using the Docker Official Image, you must first mirror the Node.js image into your organization and then use it as your base image. Follow the instructions in the [DHI quickstart](/dhi/get-started/) to create a mirrored repository for Node.js.
 
-Mirrored repositories must start with `dhi-`, for example: `FROM <your-namespace>/dhi-node:<tag>`. In the following Dockerfile, the `FROM` instruction uses `<your-namespace>/dhi-node:22` as the base image.
+Mirrored repositories must start with `dhi-`, for example: `FROM <your-namespace>/dhi-node:<tag>`. In the following Dockerfile, the `FROM` instruction uses `<your-namespace>/dhi-node:24-alpine3.22-dev` as the base image.
 
 ```dockerfile
 # ========================================
 # Optimized Multi-Stage Dockerfile
 # Node.js TypeScript Application (Using DHI)
 # ========================================
 
-FROM <your-namespace>/dhi-node:22 AS base
+FROM <your-namespace>/dhi-node:24-alpine3.22-dev AS base
 
 # Set working directory
 WORKDIR /app
@@ -414,8 +419,7 @@ CMD ["npm", "run", "dev:docker"]
 # ========================================
 # Production Stage
 # ========================================
-ARG NODE_VERSION=22.21.0-alpine3.21
-FROM node:${NODE_VERSION} AS production
+FROM <your-namespace>/dhi-node:24-alpine3.22-dev AS production
 
 # Set working directory
 WORKDIR /app
@@ -465,7 +469,7 @@ CMD ["npm", "run", "test:coverage"]
 ```
 
 {{< /tab >}}
-{{< tab name="Using the official Docker image" >}}
+{{< tab name="Using the Docker Official Image" >}}
 
 Now you need to create a production-ready multi-stage Dockerfile. Replace the generated Dockerfile with the following optimized configuration:
 
@@ -475,7 +479,7 @@ Now you need to create a production-ready multi-stage Dockerfile. Replace the ge
 # Node.js TypeScript Application
 # ========================================
 
-ARG NODE_VERSION=22.21.0-alpine3.21
+ARG NODE_VERSION=24.11.1-alpine
 FROM node:${NODE_VERSION} AS base
 
 # Set working directory
@@ -562,7 +566,7 @@ CMD ["npm", "run", "dev:docker"]
 # ========================================
 # Production Stage
 # ========================================
-ARG NODE_VERSION=22.21.0-alpine3.21
+ARG NODE_VERSION=24.11.1-alpine
 FROM node:${NODE_VERSION} AS production
 
 # Set working directory