From 59b9d7bb6a51193797151efae17008dc1d659e71 Mon Sep 17 00:00:00 2001 From: Robin Davidson <41165509+RMDavidson@users.noreply.github.com> Date: Wed, 16 Apr 2025 13:52:47 -0400 Subject: [PATCH] Update runtime-control.md Removed gerund from line 22 - controlling vs control --- .../nginx/admin-guide/basic-functionality/runtime-control.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/nginx/admin-guide/basic-functionality/runtime-control.md b/content/nginx/admin-guide/basic-functionality/runtime-control.md index 7f61904a0..9fb4536c7 100644 --- a/content/nginx/admin-guide/basic-functionality/runtime-control.md +++ b/content/nginx/admin-guide/basic-functionality/runtime-control.md @@ -19,7 +19,7 @@ The main purpose of the master process is to read and evaluate configuration fil The worker processes do the actual processing of requests. NGINX relies on OS-dependent mechanisms to efficiently distribute requests among worker processes. The number of worker processes is defined by the [worker_processes](https://nginx.org/en/docs/ngx_core_module.html#worker_processes) directive in the **nginx.conf** configuration file and can either be set to a fixed number or configured to adjust automatically to the number of available CPU cores. -## Controlling NGINX +## Control NGINX To reload your configuration, you can stop or restart NGINX, or send signals to the master process. A signal can be sent by running the `nginx` command (invoking the NGINX executable) with the `-s` argument.