Typo

doc/apps/req.pod

diff --git a/doc/apps/req.pod b/doc/apps/req.pod
index 10e4e12..7a3b6bb 100644
--- a/doc/apps/req.pod
+++ b/doc/apps/req.pod
@@ -512,13 +512,13 @@
 
 The header and footer lines in the B<PEM> format are normally:
 
- -----BEGIN CERTIFICATE REQUEST----
- -----END CERTIFICATE REQUEST----
+ -----BEGIN CERTIFICATE REQUEST-----
+ -----END CERTIFICATE REQUEST-----
 
 some software (some versions of Netscape certificate server) instead needs:
 
- -----BEGIN NEW CERTIFICATE REQUEST----
- -----END NEW CERTIFICATE REQUEST----
+ -----BEGIN NEW CERTIFICATE REQUEST-----
+ -----END NEW CERTIFICATE REQUEST-----
 
 which is produced with the B<-newhdr> option but is otherwise compatible.
 Either form is accepted transparently on input.

doc/apps/smime.pod

diff --git a/doc/apps/smime.pod b/doc/apps/smime.pod
index fa5d23e..2453dd2 100644
--- a/doc/apps/smime.pod
+++ b/doc/apps/smime.pod
@@ -340,8 +340,8 @@
 signature by line wrapping the base64 encoded structure and surrounding
 it with:
 
- -----BEGIN PKCS7----
- -----END PKCS7----
+ -----BEGIN PKCS7-----
+ -----END PKCS7-----
 
 and using the command, 
 

doc/apps/x509.pod

diff --git a/doc/apps/x509.pod b/doc/apps/x509.pod
index 9f7eba4..0b53fb1 100644
--- a/doc/apps/x509.pod
+++ b/doc/apps/x509.pod
@@ -643,18 +643,18 @@
 
 The PEM format uses the header and footer lines:
 
- -----BEGIN CERTIFICATE----
- -----END CERTIFICATE----
+ -----BEGIN CERTIFICATE-----
+ -----END CERTIFICATE-----
 
 it will also handle files containing:
 
- -----BEGIN X509 CERTIFICATE----
- -----END X509 CERTIFICATE----
+ -----BEGIN X509 CERTIFICATE-----
+ -----END X509 CERTIFICATE-----
 
 Trusted certificates have the lines
 
- -----BEGIN TRUSTED CERTIFICATE----
- -----END TRUSTED CERTIFICATE----
+ -----BEGIN TRUSTED CERTIFICATE-----
+ -----END TRUSTED CERTIFICATE-----
 
 The conversion to UTF8 format used with the name options assumes that
 T61Strings use the ISO8859-1 character set. This is wrong but Netscape