nginx is lower case

docs/effective-volto/deployment/seamlessmode.md

@@ -30,11 +30,11 @@ The first question, *"what is my domain name?"* can be answered by looking at th
 The second question is a lot harder to answer, there can be so many unknowns, so, instead, we have a few layers of conventions and configuration variables.
 
 - If you're running Volto for development, the Plone backend is exposed from the frontend (`localhost:3000`) via a "devproxy" that assumes that the Plone backend is at `http://localhost:8080/Plone`. You can override it with [`RAZZLE_DEV_PROXY_API_PATH`](https://github.com/plone/volto/blob/5eb332829956dbf0505283b176008c9364ccf2f9/src/config/index.js#L101).
-- If you're running in production, the Plone backend is assumed to be exposed at the same domain, but available via the special traversal path, the `++api++`. So you need to add aditional rewrite rules in your Apache or Nginx proxy server to directly redirect those requests to the Plone backend.
+- If you're running in production, the Plone backend is assumed to be exposed at the same domain, but available via the special traversal path, the `++api++`. So you need to add aditional rewrite rules in your Apache or nginx proxy server to directly redirect those requests to the Plone backend.
 - Before the `++api++` traverser was developed, we would configure the proxy server to serve Plone directly via a `/api` subpath and the `_vh_api` VirtualHostMonster suffix. Then we would configure Volto with the `RAZZLE_API_PATH` variable. This is still available and works.
 - If you want the Volto nodejs server to communicate directly with the Plone backend via the internal network (for example, when running a Docker stack), you can use the `RAZZLE_INTERNAL_API_PATH` setting to configure the address of the Plone backend.
 
-## Nginx example config for seamless mode deployments
+## nginx example config for seamless mode deployments
 
 ```nginx
 upstream backend {

docs/glossary.md

@@ -302,8 +302,8 @@ Traefik
     It simplifies the deployment and routing of services and is particularly well-suited for cloud-native and containerized environments,
     offering features like automatic service discovery, middleware plugins, and robust security options.
 
-Nginx
-    [Nginx](https://nginx.org/en/) is a high-performance web server, reverse proxy, and load balancer that is known for its speed, reliability, and flexibility.
+nginx
+    [nginx](https://nginx.org/en/) is a high-performance web server, reverse proxy, and load balancer that is known for its speed, reliability, and flexibility.
     It can also serve as a mail proxy server and provides features for HTTP and TCP/UDP applications, making it a popular choice for serving web content,
     optimizing resource utilization, and enhancing web performance and security.
 

docs/mastering-plone-5/installation.md

@@ -100,7 +100,7 @@ See all the ways you can [set up Plone](https://plone.org/download)
 The way we are setting up a Plone site during this class may be adequate for a small site
 — or even a large one that's not very busy — but you are likely to want to do much more if you are using Plone for anything demanding.
 
-- Using a production web server like Apache or Nginx for URL rewriting, SSL and combining multiple, best-of-breed solutions into a single web site.
+- Using a production web server like Apache or nginx for URL rewriting, SSL and combining multiple, best-of-breed solutions into a single web site.
 - Reverse proxy caching with a tool like Varnish to improve site performance.
 - Load balancing to make best use of multiple core CPUs and even multiple servers.
 - Optimizing cache headers and Plone's internal caching schemes with plone.app.caching.

docs/plone-deployment/plone-stack.md

@@ -16,7 +16,7 @@ This guide won't cover the integration of a web accelerator or the setup of an e
 
 ### Web server
 
-The web server, accessible externally on ports 80 and 443, handles the routing and rewriting of HTTP requests to the Plone frontend and backend, and is tasked with TLS termination. While {term}`Nginx` and {term}`Traefik` are recommended, other web servers can also be employed. This training will exclusively utilize Traefik.
+The web server, accessible externally on ports 80 and 443, handles the routing and rewriting of HTTP requests to the Plone frontend and backend, and is tasked with TLS termination. While {term}`nginx` and {term}`Traefik` are recommended, other web servers can also be employed. This training will exclusively utilize Traefik.
 
 To understand the rewrite rules used in Traefik, please read our reference about {term}`Zope`'s {doc}`virtual-host`.