diff --git a/Servers & Workflows/Linux/Automation/Puppet/Puppet Bolt.md b/Servers & Workflows/Linux/Automation/Puppet/Puppet Bolt.md
index e447fd3..ddbf896 100644
--- a/Servers & Workflows/Linux/Automation/Puppet/Puppet Bolt.md	
+++ b/Servers & Workflows/Linux/Automation/Puppet/Puppet Bolt.md	
@@ -182,7 +182,7 @@ You can find the [WinRM Enablement Script](https://docs.bunny-lab.io/Docker%20%2
 At this point, you should finally be ready to connect to Windows and Linux devices and run commands on them ad-hoc.  Puppet Bolt Modules and Plans will be discussed further down the road.
 
 ??? example "Example Output of `bolt command run whoami -t domain_controllers --no-ssl-verify`"
-    You should expect to see output similar to the following.  This is what you will see when leveraging Kerberos on Windows devices.
+    You should expect to see output similar to the following.  This is what you will see when leveraging WinRM via Kerberos on Windows devices.
     ``` sh
     [root@lab-puppet-01 bolt-lab]# bolt command run whoami -t domain_controllers --no-ssl-verify
     CLI arguments ["ssl-verify"] might be overridden by Inventory: /tmp/bolt-lab/inventory.yaml [ID: cli_overrides]
@@ -197,7 +197,7 @@ At this point, you should finally be ready to connect to Windows and Linux devic
     ```
 
 ??? example "Example Output of `bolt command run whoami -t linux_servers`"
-    You should expect to see output similar to the following.  This is what you will see when leveraging Kerberos on Windows devices.
+    You should expect to see output similar to the following.  This is what you will see when leveraging native SSH on Linux devices.
     ``` sh
     [root@lab-puppet-01 bolt-lab]# bolt command run whoami -t linux_servers
     CLI arguments ["ssl-verify"] might be overridden by Inventory: /tmp/bolt-lab/inventory.yaml [ID: cli_overrides]