diff --git a/doc/source/install/advanced_deployment/deployment_status.rst b/doc/source/install/advanced_deployment/deployment_status.rst
index a6497945..1f11221d 100644
--- a/doc/source/install/advanced_deployment/deployment_status.rst
+++ b/doc/source/install/advanced_deployment/deployment_status.rst
@@ -4,14 +4,13 @@ Since Heat is no longer the source of authority on the status of the overcloud
 deployment, a new tripleoclient command is available to show the overcloud
 deployment status::
 
-    openstack overcloud plan deployment status
+    openstack overcloud status
 
 The output will report the status of the deployment, taking into consideration
 the result of all the steps to do the full deployment. The following is an
 example of the sample output::
 
-    (undercloud) [stack@undercloud ]$ openstack overcloud plan deployment status
-
+    [stack@undercloud ]$ openstack overcloud status
 
     +-----------+---------------------+---------------------+-------------------+
     | Plan Name |       Created       |       Updated       | Deployment Status |
@@ -19,6 +18,20 @@ example of the sample output::
     | overcloud | 2018-05-03 21:24:50 | 2018-05-03 21:27:59 |   DEPLOY_SUCCESS  |
     +-----------+---------------------+---------------------+-------------------+
 
+A different plan name can be specified with ``--plan``::
+
+    [stack@undercloud ]$ openstack overcloud status --plan my-deployment
+
+    +---------------+---------------------+---------------------+-------------------+
+    | Plan Name     |       Created       |       Updated       | Deployment Status |
+    +-----------+-------------------------+---------------------+-------------------+
+    | my-deployment | 2018-05-03 21:24:50 | 2018-05-03 21:27:59 |   DEPLOY_SUCCESS  |
+    +---------------+---------------------+---------------------+-------------------+
+
+Deployment failures can also be shown with a new command::
+
+    [stack@undercloud ]$ openstack overcloud failures --plan my-deployment
+
 .. note::
 
     Heat CLI commands such as ``openstack stack failures list`` can still be used