From 659e8f8913c404d14c739919c683d82aa1ebfee2 Mon Sep 17 00:00:00 2001
From: Miguel Grinberg <miguel.grinberg@gmail.com>
Date: Fri, 5 Sep 2014 17:51:57 +0000
Subject: [PATCH] replaced incorrect reference to nova-manage with
 keystone-manage

This is a reference to nova-manage in a keystone specific
section. The correct tool is keystone-manage.

Change-Id: I5ec435228a65e0731482a622bbc18a5215a24f20
Closes-Bug: 1366144
---
 doc/common/section_keystone_certificates-for-pki.xml | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/doc/common/section_keystone_certificates-for-pki.xml b/doc/common/section_keystone_certificates-for-pki.xml
index 059b61b47e..823f5a7c5b 100644
--- a/doc/common/section_keystone_certificates-for-pki.xml
+++ b/doc/common/section_keystone_certificates-for-pki.xml
@@ -26,10 +26,11 @@
             the account that is going to sign tokens. When generating
             files with the <command>keystone-manage
                 pki_setup</command> command, your best option is to
-            run as the pki user. If you run nova-manage as root, you
-            can append --keystone-user and --keystone-group parameters
-            to set the user name and group keystone is going to run
-            under.</para>
+            run as the pki user. If you run <command>keystone-manage</command>
+            as root, you can append <parameter>--keystone-user</parameter>
+            and <parameter>--keystone-group</parameter>
+            parameters to set the user name and group keystone is going
+            to run under.</para>
     </warning>
     <para>The values that specify where to read the certificates are
         under the <literal>[signing]</literal> section of the