[deployment-guide/comm-rel-14: 630/677] Rephrased the admonition a bit.

[Jaromir Hradilek]

commit 1ec000d507cd905f4abd1dd6ce756a5b5109c971
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Fri Oct 22 18:18:15 2010 +0200

    Rephrased the admonition a bit.

 en-US/The_Apache_HTTP_Server.xml |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/en-US/The_Apache_HTTP_Server.xml b/en-US/The_Apache_HTTP_Server.xml
index 545eadf..f92c64d 100644
--- a/en-US/The_Apache_HTTP_Server.xml
+++ b/en-US/The_Apache_HTTP_Server.xml
@@ -3922,7 +3922,7 @@ SSLCertificateKeyFile /etc/pki/tls/private/<replaceable>hostname</replaceable>.k
       <important>
         <title>Important: Replacing an Existing Certificate</title>
         <para>
-          If the server already has a valid certificate and you are replacing it with a new one, specify a different serial number, so that client browsers are notified of this change, update to this new certificate, and do not fail to access the page. To generate a certificate with a custom serial number, use the following command instead:
+          If the server already has a valid certificate and you are replacing it with a new one, specify a different serial number, so that client browsers are notified of this change, update to this new certificate, and do not fail to access the page. To do so, use the following command instead:
         </para>
         <screen>~]# <command>openssl req -new -set_serial <replaceable>number</replaceable> -key <replaceable>hostname</replaceable>.key -out <replaceable>hostname</replaceable>.crt</command></screen>
       </important>