From 56dc24d48315285ba3c0395d315282275217e597 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Lutz=20J=C3=A4nicke?= <jaenicke@openssl.org>
Date: Thu, 14 Nov 2002 21:50:30 +0000
Subject: Use =back to finish =over (found using pod2latex). Submitted by:
 Reviewed by: PR:

---
 doc/crypto/ASN1_generate_nconf.pod | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'doc')

diff --git a/doc/crypto/ASN1_generate_nconf.pod b/doc/crypto/ASN1_generate_nconf.pod
index d54df3ae96..c4c683b2a6 100644
--- a/doc/crypto/ASN1_generate_nconf.pod
+++ b/doc/crypto/ASN1_generate_nconf.pod
@@ -109,7 +109,7 @@ should be a section name which will contain the contents. The
 field names are ignored and the values are in the generated
 string format. If B<value> is absent the the content will be empty.
 
-=cut
+=back
 
 =head2 MODIFIERS
 
@@ -151,7 +151,7 @@ then the value string must be a valid B<UTF8> string. For B<HEX> the output must
 be a set of hex digits. B<BITLIST> (which is only valid for a BIT STRING) is a
 comma separated list of set bits.
 
-=cut
+=back
 
 =head1 EXAMPLES
 
-- 
cgit v1.2.3