diff --git a/draft-ietf-lsvr-l3dl.xml b/draft-ietf-lsvr-l3dl.xml
index 331314d..5c98ca6 100644
--- a/draft-ietf-lsvr-l3dl.xml
+++ b/draft-ietf-lsvr-l3dl.xml
@@ -1458,7 +1458,7 @@ uint32_t sbox_checksum_32(const uint8_t *b, const size_t n)
       sub-TLV-->.</t>
 
       <t>If there are one or more open BGP sessions, <!-- absent a BGP
-      Restart sub-TLV, --> receipt of a new BGP ULPC PDU SHOULD not
+      Restart sub-TLV, --> receipt of a new BGP ULPC PDU SHOULD NOT
       affect these sessions.  The received data are stored for a future
       session restart.</t>
       
@@ -1469,7 +1469,7 @@ uint32_t sbox_checksum_32(const uint8_t *b, const size_t n)
 
       <t>For each BGP peering on a link here MUST be one agreed
       encapsulation, and the addresses used MUST be in the corresponding
-      L3DP IPv4/IPv6 Announcement PDUs.  If the choice is ambiguous, an
+      L3DL IPv4/IPv6 Announcement PDUs.  If the choice is ambiguous, an
       Attribute may be used to signal preferences.</t>
 
       <t>If a peering address has been announced as a loopback,
@@ -1590,7 +1590,7 @@ uint32_t sbox_checksum_32(const uint8_t *b, const size_t n)
         configuration of the environment, it might be a simple MD5 key
         (see <xref target="RFC2385"/>), the name of a key chain in a
         KARP database (see <xref target="RFC7210"/>), or one of multiple
-        Authentication sub-TLVs to support hop<xref
+        Authentication sub-TLVs to support <xref
         target="RFC4808"/>.</t>
         
 <!--