README.md in foreman_bootdisk-3.0.0 vs README.md in foreman_bootdisk-3.1.0

@@ -140,16 +140,23 @@
 instead of being stored in the image.
 
 To generate the image from the web interface, view the host page, click the
 "Boot disk" button and select "Host 'FQDN' image".
 
-To generate from the command line:
+To generate from the command line on the Foreman server:
 
     foreman-rake bootdisk:generate:host NAME=foo.example.com
 
 Optionally set `OUTPUT=/path/foo.iso` to change the output destination.
 
+To generate using the Hammer CLI, install the [hammer_cli_foreman_bootdisk](https://github.com/theforeman/hammer_cli_foreman_bootdisk)
+plugin and run:
+
+    hammer bootdisk host --host client.example.com
+
+See the hammer_cli_foreman_bootdisk documentation for more advanced usage.
+
 ### Generic image
 
 This provides a single ISO that can be used by all registered hosts, but since
 IP details can't be stored inside, it requires a DHCP pool on the network to
 bootstrap.  It will boot and contact Foreman for template of a registered host
@@ -160,14 +167,21 @@
 address statically for the installed system via the kickstart file.
 
 To generate the image from the web interface, view a host page, click the
 "Boot disk" button and select "Generic image".
 
-To generate from the command line:
+To generate from the command line on the Foreman server:
 
     foreman-rake bootdisk:generate:generic
 
 Optionally set `OUTPUT=/path/foo.iso` to change the output destination.
+
+To generate using the Hammer CLI, install the [hammer_cli_foreman_bootdisk](https://github.com/theforeman/hammer_cli_foreman_bootdisk)
+plugin and run:
+
+    hammer bootdisk generic
+
+See the hammer_cli_foreman_bootdisk documentation for more advanced usage.
 
 ### Host group images
 
 TODO