diff --git a/ietf-lamps-hp/draft-ietf-lamps-header-protection.mkd b/ietf-lamps-hp/draft-ietf-lamps-header-protection.mkd
index 49fb337e..f0c1d5ae 100644
--- a/ietf-lamps-hp/draft-ietf-lamps-header-protection.mkd
+++ b/ietf-lamps-hp/draft-ietf-lamps-header-protection.mkd
@@ -514,8 +514,7 @@ There may also be an additional MIME layer with media type
 Message (wrapped in a "message/RFC822") along with other MIME part(s).
 
 
-#### Alternative Option Autocrypt "Protected Headers" (Ex-"Memory
-     Hole") {#option-ex-memory-hole}
+#### Alternative Option Autocrypt "Protected Headers" (Ex-"Memory Hole") {#option-ex-memory-hole}
 
 An alternative Option (based on the former autocrypt "Memory Hole" approach)
 to be considered, is described in
diff --git a/ietf-lamps-hp/review/draft-ietf-lamps-header-protection-00-pre20200626.html b/ietf-lamps-hp/review/draft-ietf-lamps-header-protection-00-pre20200626.html
index 23c8e3a7..98bcc381 100644
--- a/ietf-lamps-hp/review/draft-ietf-lamps-header-protection-00-pre20200626.html
+++ b/ietf-lamps-hp/review/draft-ietf-lamps-header-protection-00-pre20200626.html
@@ -754,11 +754,8 @@ signature.
 <p id="rfc.section.4.1.1.1.p.9">The Original Message itself may contain any MIME structure.</p>
 <p id="rfc.section.4.1.1.1.p.10">There may also be an additional MIME layer with media type &#8220;multipart/mixed&#8221; in the Outer Message Body to contain the Inner Message (wrapped in a &#8220;message/RFC822&#8221;) along with other MIME part(s).</p>
 <h1 id="rfc.section.4.1.1.2">
-<a href="#rfc.section.4.1.1.2">4.1.1.2.</a> <a href="#alternative-option-autocrypt-protected-headers-ex-memory" id="alternative-option-autocrypt-protected-headers-ex-memory">Alternative Option Autocrypt &#8220;Protected Headers&#8221; (Ex-&#8220;Memory</a>
+<a href="#rfc.section.4.1.1.2">4.1.1.2.</a> <a href="#option-ex-memory-hole" id="option-ex-memory-hole">Alternative Option Autocrypt &#8220;Protected Headers&#8221; (Ex-&#8220;Memory Hole&#8221;)</a>
 </h1>
-<pre>
- Hole") {#option-ex-memory-hole}
-</pre>
 <p id="rfc.section.4.1.1.2.p.1">An alternative Option (based on the former autocrypt &#8220;Memory Hole&#8221; approach) to be considered, is described in <a href="#I-D.autocrypt-lamps-protected-headers" class="xref">[I-D.autocrypt-lamps-protected-headers]</a>.</p>
 <p id="rfc.section.4.1.1.2.p.2">Unlike the option described in <a href="#option-smime-spec" class="xref">Section 4.1.1.1</a>, this option does not use a &#8220;message/RFC822&#8221; wrapper to unambigously delimit the Inner Message.</p>
 <p id="rfc.section.4.1.1.2.p.3">The MIME structure of an Email message looks as follows:</p>
diff --git a/ietf-lamps-hp/review/draft-ietf-lamps-header-protection-00-pre20200626.txt b/ietf-lamps-hp/review/draft-ietf-lamps-header-protection-00-pre20200626.txt
index 3ec31baf..d7249ad2 100644
--- a/ietf-lamps-hp/review/draft-ietf-lamps-header-protection-00-pre20200626.txt
+++ b/ietf-lamps-hp/review/draft-ietf-lamps-header-protection-00-pre20200626.txt
@@ -570,8 +570,7 @@ Internet-Draft          Header Protection S/MIME               June 2020
    part(s).
 
 4.1.1.2.  Alternative Option Autocrypt "Protected Headers" (Ex-"Memory
-
-    Hole") {#option-ex-memory-hole}
+          Hole")
 
    An alternative Option (based on the former autocrypt "Memory Hole"
    approach) to be considered, is described in
@@ -613,6 +612,7 @@ Internet-Draft          Header Protection S/MIME               June 2020
 
 
 
+
 Hoeneisen & Melnikov    Expires December 28, 2020              [Page 11]
 
 Internet-Draft          Header Protection S/MIME               June 2020