diff --git a/draft-ymbk-idr-l3nd.xml b/draft-ymbk-idr-l3nd.xml
index 07032ca..c72e391 100644
--- a/draft-ymbk-idr-l3nd.xml
+++ b/draft-ymbk-idr-l3nd.xml
@@ -498,13 +498,13 @@ Flags (bit):
     client and open the transport session (send SYN) toward the peer
     with the lower IP address.</t>
 
-    <t>The server, the sender of the HELLO with from the lower IP
-    address, listens on the advertised port for the TLS/TCP session
-    open.  The receiver of the acceptable HELLO, the TLS/TCP client,
-    initiates a TLS or raw TCP session toward the sender of the HELLO,
-    the TLS/TCP server, preferably TLS, as advertised.  If TLS, the
-    server has chosen and signaled either a self-signed certificate or
-    one configured from the operational CA trusted by both parties, as
+    <t>The server, the sender of the HELLO from the lower IP address,
+    listens on the advertised port for the TLS/TCP session open.  The
+    receiver of the acceptable HELLO, the TLS/TCP client, initiates a
+    TLS or raw TCP session toward the sender of the HELLO, the TLS/TCP
+    server, preferably TLS, as advertised.  If TLS, the server has
+    chosen and signaled either a self-signed certificate or one
+    configured from the operational CA trusted by both parties, as
     negotiated in the HELLO exchange.</t>
 
     <t>Once the TLS/TCP session is established, if its interface is
@@ -514,7 +514,7 @@ Flags (bit):
     HELLOs.</t>
 
     <t>If the TLS/TCP open fails, then this SHOULD be logged and the
-    parties MUST go back to the initial state and try HELLO.  Loggin
+    parties MUST go back to the initial state and try HELLO.  Logging
     SHOULD be rate limited.</t>
 
     <t>Should an interface with an established TLS/TCP session be
@@ -591,9 +591,9 @@ Flags (bit):
 
     <t>The Serial Number is a monotonically increasing four octet value
     representing the sender's state at the time of sending the last PDU.
-    It may be an non-negative integer, a timestamp, etc.  If
-    incrementing the Serial Number would cause it to be zero, it should
-    be incremented again.</t>
+    It may be a non-negative integer, a timestamp, etc.  If incrementing
+    the Serial Number would cause it to be zero, it should be
+    incremented again.</t>
 
     <t>On session restart (new OPEN, same Nonce), a receiver MAY send
     the last received Serial Number to tell the sender to only send data
@@ -791,8 +791,9 @@ Flags (bit):
       interface in a session as configuration changes.</t>
 
       <t>The Receiver MUST acknowledge the Encapsulation PDU with an ACK
-      PDU (<xref target="ack"/>) with the PDU Type being that of the
-      type PDU being announced, see <xref target="ack"/>.</t>
+      PDU (<xref target="ack"/>) with the Type field being that of the
+      Type of the Encapsulation PDU being announced, see <xref
+      target="ack"/>.</t>
 
       <t>If the Sender does not receive an ACK in a configurable
       interval (default five seconds), they SHOULD retransmit.  After a
@@ -1073,8 +1074,8 @@ Flags (bit):
     the vendor/enterprise needs multiple PDU types.</t>
 
     <t>As with Encapsulation PDUs, a receiver of a Vendor PDU MUST
-    respond with an ACK or an ERROR PDU.  Similarly, a Vendor PDU MUST
-    only be sent over an open session.</t>
+    respond with an ACK PDU, possibly signalling an error.  Similarly, a
+    Vendor PDU MUST only be sent over an open session.</t>
 
     </section>