smaller edits to align

intarchboard · Feb 21, 2025 · c96238c · c96238c
1 parent 6caacd2
commit c96238c
Showing 1 changed file with 5 additions and 7 deletions.
diff --git a/draft-kuehlewind-iab-rfc4053bis.md b/draft-kuehlewind-iab-rfc4053bis.md
@@ -381,9 +381,9 @@ other organization.
 #  Responding to Incoming Liaison Statements
 
    Any incoming liaison statement that indicates that it is for
-   "Comment" or for "Action" requires a response by the deadline.
+   "Action" requires a response by the deadline.
    It is the responsibility of the (co)chair(s) of
-   the addressed organization to ensure that a response is generated by
+   the addressed group to ensure that a response is generated by
    the deadline if a respone is intended.
 
 ##  Responding to Requests for Information
@@ -451,7 +451,7 @@ other organization.
 
 It is important that appropriate leadership review be made of
 proposed IETF liaison statements and that those writing such
-statements, who claim to be speaking on behalf of IETF, are truly
+statements, who claim to be speaking on behalf of a group in the IETF, are truly
 representing IETF views.
 
 For a liaison statement generated on behalf of an IETF WG, the WG
@@ -483,7 +483,7 @@ the IAB Chair on the message.
 In cases where prior agreement was not obtained as outlined above,
 and the designated authority (AD, IETF Chair, or IAB Chair) in fact
 does not agree with the message, the designated authority will work
-with the liaison manager to follow up as appropriate, including
+with the liaison manager or IAB to follow up as appropriate, including
 emitting a revised liaison statement if necessary.  Clearly, this is
 a situation best avoided by assuring appropriate agreement in advance
 of sending the liaison message.
@@ -499,9 +499,7 @@ of sending the liaison message.
    have also used the liaison statement process to impose deadlines on
    IETF activities, which has been frustrating for all concerned - the
    IETF because it does not accept such deadlines, and other
-   organizations because they feel ignored.
-
-   For this reason the submission process is automated.  While the IETF
+   organizations because they feel ignored. While the IETF
    cannot rate-limit the submitters, it can manage its internal
    pipelines.