diff --git a/content/waf/install/update-signatures.md b/content/waf/install/update-signatures.md
index 1f453afa0..0a82ca6a7 100644
--- a/content/waf/install/update-signatures.md
+++ b/content/waf/install/update-signatures.md
@@ -32,4 +32,15 @@ They will be named something in the following list:
 - `app-protect-bot-signatures`
 - `app-protect-threat-campaigns`
 
-You can update these packages independently of the core F5 WAF for NGINX packages, ensuring you always have the latest signatures.
\ No newline at end of file
+You can update these packages independently of the core F5 WAF for NGINX packages, ensuring you always have the latest signatures.
+
+## Apply the updated signatures
+
+Updated signatures don't take effect until you reload NGINX. Until you reload, F5 WAF for NGINX keeps running the previous signatures.
+
+A reload is enough. You don't need to restart NGINX.
+
+To apply the updated signatures, run one of the following commands:
+
+- On all platforms: `nginx -s reload`
+- On systemd-based platforms (Amazon Linux, Debian, Oracle Linux, RHEL, Rocky Linux, Ubuntu): `sudo systemctl reload nginx`
\ No newline at end of file
diff --git a/content/waf/install/virtual-environment.md b/content/waf/install/virtual-environment.md
index 8a0a385b6..c84ef1d20 100644
--- a/content/waf/install/virtual-environment.md
+++ b/content/waf/install/virtual-environment.md
@@ -427,10 +427,10 @@ server {
 
 {{< /tabs >}}
 
-Once you have updated your configuration files, you can reload NGINX to apply the changes. You have two options depending on your environment:
+Once you have updated your configuration files, reload NGINX to apply the changes:
 
-- `nginx -s reload`
-- `sudo systemctl reload nginx`
+- On all platforms: `nginx -s reload`
+- On systemd-based platforms (Amazon Linux, Debian, Oracle Linux, RHEL, Rocky Linux, Ubuntu): `sudo systemctl reload nginx`
 
 ## Post-installation checks