[feat] update NGINX to uppercase

Author: kristiyan-velkov

content/guides/angular/containerize.md

@@ -136,7 +136,7 @@ Mirrored repositories must start with `dhi-`, for example: `FROM <your-namespace
 # Stage 1: Build the Angular Application
 # =========================================
 
-# Use a lightweight Node.js image for building (customizable via ARG)
+# Use a lightweight DHI Node.js image for building
 FROM <your-namespace>/dhi-node:24-alpine3.22-dev AS builder
 
 # Set the working directory inside the container
@@ -155,15 +155,15 @@ COPY . .
 RUN npm run build 
 
 # =========================================
-# Stage 2: Prepare Nginx to Serve Static Files
+# Stage 2: Prepare NGINX to Serve Static Files
 # =========================================
 
 FROM <your-namespace>/dhi-nginx:1.28.0-alpine3.21-dev AS runner
 
 # Copy custom Nginx config
 COPY nginx.conf /etc/nginx/nginx.conf
 
-# Copy the static build output from the build stage to Nginx's default HTML serving directory
+# Copy the static build output from the build stage to NGINX's default HTML serving directory
 COPY --chown=nginx:nginx --from=builder /app/dist/*/browser /usr/share/nginx/html
 
 # Use a non-root user for security best practices
@@ -173,7 +173,7 @@ USER nginx
 # Note: The default NGINX container now listens on port 8080 instead of 80 
 EXPOSE 8080
 
-# Start Nginx directly with custom config
+# Start NGINX directly with custom config
 ENTRYPOINT ["nginx", "-c", "/etc/nginx/nginx.conf"]
 CMD ["-g", "daemon off;"]
 ```
@@ -209,7 +209,7 @@ COPY . .
 RUN npm run build 
 
 # =========================================
-# Stage 2: Prepare Nginx to Serve Static Files
+# Stage 2: Prepare NGINX to Serve Static Files
 # =========================================
 
 FROM nginxinc/nginx-unprivileged:${NGINX_VERSION} AS runner

content/guides/angular/deploy.md

@@ -85,7 +85,7 @@ This manifest defines two key Kubernetes resources, separated by `---`:
 - Deployment
   Deploys a single replica of your Angular application inside a pod. The pod uses the Docker image built and pushed by your GitHub Actions CI/CD workflow  
   (refer to [Automate your builds with GitHub Actions](configure-github-actions.md)).  
-  The container listens on port `8080`, which is typically used by [Nginx](https://nginx.org/en/docs/) to serve your production Angular app.
+  The container listens on port `8080`, which is typically used by [NGINX](https://nginx.org/en/docs/) to serve your production Angular app.
 
 - Service (NodePort) 
   Exposes the deployed pod to your local machine.  

content/guides/angular/develop.md

@@ -15,7 +15,7 @@ Complete [Containerize Angular application](containerize.md).
 
 ## Overview
 
-In this section, you'll learn how to set up both production and development environments for your containerized Angular application using Docker Compose. This setup allows you to serve a static production build via Nginx and to develop efficiently inside containers using a live-reloading dev server with Compose Watch.
+In this section, you'll learn how to set up both production and development environments for your containerized Angular application using Docker Compose. This setup allows you to serve a static production build via NGINX and to develop efficiently inside containers using a live-reloading dev server with Compose Watch.
 
 You’ll learn how to:
 - Configure separate containers for production and development
@@ -97,7 +97,7 @@ services:
           path: .
           target: /app
 ```
-- The `angular-prod` service builds and serves your static production app using Nginx.
+- The `angular-prod` service builds and serves your static production app using NGINX.
 - The `angular-dev` service runs your Angular development server with live reload and hot module replacement.
 - `watch` triggers file sync with Compose Watch.