diff --git a/README.md b/README.md index 1dd89cf711..5f29d0321b 100644 --- a/README.md +++ b/README.md @@ -48,7 +48,7 @@ NGINX Agent runs as a companion process on a system running NGINX. It provides g ![How NGINX Agent works](docs/agent-flow.png "How NGINX Agent works") ## Configuration Management -NGINX Agent provides an API interface for submission of updated configuration files. Upon receipt of a new file, it checks the output of `nginx -V` to determine the location of existing configurations. It then validates the new configuration with `nginx -t` before applying it via a NOHUP signal to the NGINX master process. +NGINX Agent provides an API interface for submission of updated configuration files. Upon receipt of a new file, it checks the output of `nginx -V` to determine the location of existing configurations. It then validates the new configuration with `nginx -t` before applying it via a signal HUP to the NGINX master process. ## Collecting Metrics NGINX Agent interfaces with NGINX process information and parses NGINX logs to calculate and report metrics. When interfacing with NGINX Plus, NGINX Agent pulls relevant information from the NGINX Plus API. Reported metrics may be aggregated by [Prometheus](https://prometheus.io/) and visualized with tools like [Grafana](https://grafana.com/). diff --git a/hugo/content/overview.md b/hugo/content/overview.md index ba29d087eb..8428524c73 100644 --- a/hugo/content/overview.md +++ b/hugo/content/overview.md @@ -28,7 +28,7 @@ NGINX Agent runs as a companion process on a system running NGINX. It provides g ## Configuration Management -NGINX Agent provides an API interface for submission of updated configuration files. Upon receipt of a new file, it checks the output of `nginx -V` to determine the location of existing configurations. It then validates the new configuration with `nginx -t` before applying it via a NOHUP signal to the NGINX master process. +NGINX Agent provides an API interface for submission of updated configuration files. Upon receipt of a new file, it checks the output of `nginx -V` to determine the location of existing configurations. It then validates the new configuration with `nginx -t` before applying it via a signal HUP to the NGINX master process. ## Collecting Metrics