Merged revisions 294049 via svnmerge from

https://origsvn.digium.com/svn/asterisk/branches/1.8

........
  r294049 | twilson | 2010-11-05 09:05:50 -0700 (Fri, 05 Nov 2010) | 2 lines

  Corret spelling and example
........

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@294050 65c4cc65-6c06-0410-ace0-fbb531ad65f3

diff --git a/contrib/scripts/ast_tls_cert b/contrib/scripts/ast_tls_cert
index 3650bff..9913520 100755 (executable)
--- a/contrib/scripts/ast_tls_cert
+++ b/contrib/scripts/ast_tls_cert
@@ -65,7 +65,7 @@ OPTIONS:
   -C  Common name (cert field)
         This should be the fully qualified domain name or IP address for
         the client or server. Make sure your certs have unique common
-        namems.
+        names.
   -O  Org name (cert field)
         An informational string (company name)
   -o  Output filename base (defaults to asterisk) 
@@ -83,8 +83,8 @@ and tlscafile=/etc/ca.crt. Since this is a self-signed key, many devices will
 require you to import the ca.crt file as a trusted cert.
 
 To create a client cert using the CA cert created by the example above:
-  ast_tls_cert -m client -c /tmp/ca.crt -k /tmp/ca.key -C "Joe User" -O \\
-    "My Company" -d /tmp -o joe_user
+  ast_tls_cert -m client -c /tmp/ca.crt -k /tmp/ca.key -C phone1.mycompany.com \\
+    -O "My Company" -d /tmp -o joe_user
 
 This will create client.crt/key/pem in /tmp. Use this if your device supports
 a client certificate. Make sure that you have the ca.crt file set up as