diff --git a/content/cumulus-linux-44/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-44/Installation-Management/Zero-Touch-Provisioning-ZTP.md
index 01f1349020..5f7985ab0a 100644
--- a/content/cumulus-linux-44/Installation-Management/Zero-Touch-Provisioning-ZTP.md
+++ b/content/cumulus-linux-44/Installation-Management/Zero-Touch-Provisioning-ZTP.md
@@ -189,7 +189,7 @@ exit 0
 
 ## Continue Provisioning
 
-Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive.
+Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive.
 
 ## Best Practices
 
diff --git a/content/cumulus-linux-50/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-50/Installation-Management/Zero-Touch-Provisioning-ZTP.md
index 4279169a36..501f30fa42 100644
--- a/content/cumulus-linux-50/Installation-Management/Zero-Touch-Provisioning-ZTP.md
+++ b/content/cumulus-linux-50/Installation-Management/Zero-Touch-Provisioning-ZTP.md
@@ -186,7 +186,7 @@ exit 0
 
 ## Continue Provisioning
 
-Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive.
+Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive.
 
 ## Best Practices
 
diff --git a/content/cumulus-linux-51/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-51/Installation-Management/Zero-Touch-Provisioning-ZTP.md
index 903d55e932..f7d176ec7b 100644
--- a/content/cumulus-linux-51/Installation-Management/Zero-Touch-Provisioning-ZTP.md
+++ b/content/cumulus-linux-51/Installation-Management/Zero-Touch-Provisioning-ZTP.md
@@ -186,7 +186,7 @@ exit 0
 
 ## Continue Provisioning
 
-Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive.
+Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive.
 
 ## Best Practices
 
diff --git a/content/cumulus-linux-510/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-510/Installation-Management/Zero-Touch-Provisioning-ZTP.md
index dab15d3c26..f0a6942516 100644
--- a/content/cumulus-linux-510/Installation-Management/Zero-Touch-Provisioning-ZTP.md
+++ b/content/cumulus-linux-510/Installation-Management/Zero-Touch-Provisioning-ZTP.md
@@ -194,7 +194,7 @@ trap error ERR
 ```
 ### Continue Provisioning
 
-Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive.
+Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive.
 
 ## Best Practices
 
diff --git a/content/cumulus-linux-511/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-511/Installation-Management/Zero-Touch-Provisioning-ZTP.md
index ec9215dafd..2136c411ac 100644
--- a/content/cumulus-linux-511/Installation-Management/Zero-Touch-Provisioning-ZTP.md
+++ b/content/cumulus-linux-511/Installation-Management/Zero-Touch-Provisioning-ZTP.md
@@ -370,7 +370,7 @@ trap error ERR
 ```
 ### Continue Provisioning
 
-Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive.
+Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive.
 
 ## Best Practices
 
diff --git a/content/cumulus-linux-512/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-512/Installation-Management/Zero-Touch-Provisioning-ZTP.md
index e48391d065..8e451f841f 100644
--- a/content/cumulus-linux-512/Installation-Management/Zero-Touch-Provisioning-ZTP.md
+++ b/content/cumulus-linux-512/Installation-Management/Zero-Touch-Provisioning-ZTP.md
@@ -371,7 +371,7 @@ trap error ERR
 
 ### Continue Provisioning
 
-Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive.
+Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive.
 
 ## Best Practices
 
diff --git a/content/cumulus-linux-52/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-52/Installation-Management/Zero-Touch-Provisioning-ZTP.md
index 68b621f614..f63aa1a423 100644
--- a/content/cumulus-linux-52/Installation-Management/Zero-Touch-Provisioning-ZTP.md
+++ b/content/cumulus-linux-52/Installation-Management/Zero-Touch-Provisioning-ZTP.md
@@ -190,7 +190,7 @@ exit 0
 
 ## Continue Provisioning
 
-Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive.
+Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive.
 
 ## Best Practices
 
diff --git a/content/cumulus-linux-53/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-53/Installation-Management/Zero-Touch-Provisioning-ZTP.md
index 00ba8ec7e4..aeee3701ba 100644
--- a/content/cumulus-linux-53/Installation-Management/Zero-Touch-Provisioning-ZTP.md
+++ b/content/cumulus-linux-53/Installation-Management/Zero-Touch-Provisioning-ZTP.md
@@ -190,7 +190,7 @@ exit 0
 
 ## Continue Provisioning
 
-Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive.
+Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive.
 
 ## Best Practices
 
diff --git a/content/cumulus-linux-54/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-54/Installation-Management/Zero-Touch-Provisioning-ZTP.md
index 00ba8ec7e4..aeee3701ba 100644
--- a/content/cumulus-linux-54/Installation-Management/Zero-Touch-Provisioning-ZTP.md
+++ b/content/cumulus-linux-54/Installation-Management/Zero-Touch-Provisioning-ZTP.md
@@ -190,7 +190,7 @@ exit 0
 
 ## Continue Provisioning
 
-Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive.
+Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive.
 
 ## Best Practices
 
diff --git a/content/cumulus-linux-55/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-55/Installation-Management/Zero-Touch-Provisioning-ZTP.md
index 00ba8ec7e4..aeee3701ba 100644
--- a/content/cumulus-linux-55/Installation-Management/Zero-Touch-Provisioning-ZTP.md
+++ b/content/cumulus-linux-55/Installation-Management/Zero-Touch-Provisioning-ZTP.md
@@ -190,7 +190,7 @@ exit 0
 
 ## Continue Provisioning
 
-Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive.
+Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive.
 
 ## Best Practices
 
diff --git a/content/cumulus-linux-56/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-56/Installation-Management/Zero-Touch-Provisioning-ZTP.md
index 00ba8ec7e4..aeee3701ba 100644
--- a/content/cumulus-linux-56/Installation-Management/Zero-Touch-Provisioning-ZTP.md
+++ b/content/cumulus-linux-56/Installation-Management/Zero-Touch-Provisioning-ZTP.md
@@ -190,7 +190,7 @@ exit 0
 
 ## Continue Provisioning
 
-Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive.
+Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive.
 
 ## Best Practices
 
diff --git a/content/cumulus-linux-57/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-57/Installation-Management/Zero-Touch-Provisioning-ZTP.md
index 00ba8ec7e4..aeee3701ba 100644
--- a/content/cumulus-linux-57/Installation-Management/Zero-Touch-Provisioning-ZTP.md
+++ b/content/cumulus-linux-57/Installation-Management/Zero-Touch-Provisioning-ZTP.md
@@ -190,7 +190,7 @@ exit 0
 
 ## Continue Provisioning
 
-Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive.
+Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive.
 
 ## Best Practices
 
diff --git a/content/cumulus-linux-58/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-58/Installation-Management/Zero-Touch-Provisioning-ZTP.md
index 804649259c..a33e5960a1 100644
--- a/content/cumulus-linux-58/Installation-Management/Zero-Touch-Provisioning-ZTP.md
+++ b/content/cumulus-linux-58/Installation-Management/Zero-Touch-Provisioning-ZTP.md
@@ -191,7 +191,7 @@ exit 0
 
 ## Continue Provisioning
 
-Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive.
+Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive.
 
 ## Best Practices
 
diff --git a/content/cumulus-linux-59/Installation-Management/Zero-Touch-Provisioning-ZTP.md b/content/cumulus-linux-59/Installation-Management/Zero-Touch-Provisioning-ZTP.md
index a9cb9cf581..19b2b319d2 100644
--- a/content/cumulus-linux-59/Installation-Management/Zero-Touch-Provisioning-ZTP.md
+++ b/content/cumulus-linux-59/Installation-Management/Zero-Touch-Provisioning-ZTP.md
@@ -208,7 +208,7 @@ trap error ERR
 ```
 ### Continue Provisioning
 
-Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISION-CASCADE` directive.
+Typically ZTP exits after executing the script locally and does not continue. To continue with provisioning so that you do not have to intervene manually or embed an Ansible callback into the script, you can add the `CUMULUS-AUTOPROVISIONING-CASCADE` directive.
 
 ## Best Practices
 
diff --git a/content/nvue-reference/Show-Commands/System-Logs.md b/content/nvue-reference/Show-Commands/System-Logs.md
index 7f256e46bd..dbdb151a9d 100644
--- a/content/nvue-reference/Show-Commands/System-Logs.md
+++ b/content/nvue-reference/Show-Commands/System-Logs.md
@@ -242,7 +242,7 @@ cumulus@switch:~$ nv show system log file brief
 
 ## <h>nv show system log file follow</h>
 
-Shows the contents of a system log file in real-time. The command shows the log file output continuously as it is updated, similar to the behavior of the tail -f command.
+Shows the contents of a system log file in real-time. The command shows the log file output continuously as it is updated, similar to the behavior of the `tail -f` command.
 
 ### Version History
 
diff --git a/content/nvue-reference/Show-Commands/Telemetry.md b/content/nvue-reference/Show-Commands/Telemetry.md
index 22d204c2ea..88ae88a7d6 100644
--- a/content/nvue-reference/Show-Commands/Telemetry.md
+++ b/content/nvue-reference/Show-Commands/Telemetry.md
@@ -809,7 +809,7 @@ processors
 
 ## <h>nv show system telemetry health internal-metrics process</h>
 
-Shows information about the telemetry health internal metrics process.
+Shows health information about the telemetry process.
 
 ### Version History
 
@@ -833,7 +833,7 @@ uptime-seconds                     65313
 
 ## <h>nv show system telemetry health internal-metrics receivers</h>
 
-Shows information about the telemetry health internal metrics receivers.
+Shows health metrics about the telemetry receivers.
 
 ### Version History
 
@@ -853,7 +853,7 @@ prometheus/global    46989135                    0
 
 ## <h>nv show system telemetry health internal-metrics processors</h>
 
-Shows information about the telemetry health internal metrics processors.
+Shows health metrics about the telemetry processors.
 
 ### Version History
 
@@ -885,7 +885,7 @@ cumulus@switch:~$ nv show system telemetry health internal-metrics processors
 
 ## <h>nv show system telemetry health internal-metrics exporters</h>
 
-Shows information about the telemetry health internal metrics exporters.
+Shows health metrics about the telemetry exporters.
 
 ### Version History
 
@@ -904,7 +904,7 @@ otlp/global     0                              1000             0            708
 
 ## <h>nv show system telemetry hft</h>
 
-Shows the high frequency telemetry configuration.
+Shows high frequency telemetry configuration.
 
 ### Version History