Merge remote-tracking branch 'origin/stage'

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
 

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
 

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
 

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
 

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
 

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
 

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
 

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
 

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
 

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
 

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
 

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
 

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
 

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
 

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
 

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