Differences

This shows you the differences between two versions of the page.

--- pilot_test_instructions_completing_auth48_using_kramdown [2025/08/29 19:14] – kramdown -> kramdown-rfc jmahoney
+++ pilot_test_instructions_completing_auth48_using_kramdown [2026/02/12 05:44] (current) – external edit 127.0.0.1
@@ Line 2: / Line 2: @@
-This page provides instructions and information regarding AUTH48 for a document that has been edited in kramdown-rfc. For information on the pilot test, please see "[[https://www.rfc-editor.org/rpc/wiki/doku.php?id=pilot_test_kramdown_rfc|RPC Pilot Test: Editing and AUTH48 in kramdown-rfc]]".
+This page provides instructions and information regarding the AUTH48 process for a document that has been edited in kramdown-rfc. For information on the pilot test, please see "[[https://www.rfc-editor.org/rpc/wiki/doku.php?id=pilot_test_kramdown_rfc|RPC Pilot Test: Editing and AUTH48 in kramdown-rfc]]".
-This process requires two approvals during AUTH48 one for the content review and a final one that includes approval of the formatting and the outputs of XML.
+This process requires two approvals from the authors during AUTH48: one for the content review and a final one that includes approval of the formatting and the outputs of XML.
 ===== Reviewing content =====
-When the document enters AUTH48, the authors should review the document content for accuracy and comprehension. Any needed updates should be sent to the RPC per the [[#submitting_updates|"Submitting updates"]] section below.
+When the document enters AUTH48, the authors should review the document content for accuracy and comprehension. Any needed updates should be sent to the RPC per the [[#submitting_updates|"Submitting updates"]] section below.  Note that format-related updates that impact the content may be updated during this time.
 At this stage, updates will be made in the **kramdown-rfc file**.
@@ Line 24: / Line 24: @@
     * references
-  * **Copyright notices and legends** \\ Authors hsould review the copyright notice and legends as defined in RFC 5378 and the Trust Legal Provisions (TLP – https://trustee.ietf.org/license-info).
+  * **Copyright notices and legends** \\ Authors should review the copyright notice and legends as defined in RFC 5378 and the Trust Legal Provisions (TLP – https://trustee.ietf.org/license-info).
@@ Line 48: / Line 48: @@
   * rfc-editor@rfc-editor.org (the RPC team)
   * other document participants, depending on the stream (e.g., IETF Stream participants include working group chairs, the responsible ADs, and the document shepherd).
-  * auth48archive@rfc-editor.org, which is a new archival mailing list to preserve AUTH48 conversations; it is not an active discussion list:
+  * auth48archive@rfc-editor.org, which is an archival mailing list to preserve AUTH48 conversations; it is not an active discussion list:
     * More info: https://mailarchive.ietf.org/arch/msg/ietf-announce/yb6lpIGh-4Q9l2USxIAe6P8O4Zc
     * The archive itself: https://mailarchive.ietf.org/arch/browse/auth48archive/
@@ Line 56: / Line 56: @@
   * An update to the provided .md file
-  * An explicit list of changes in this format<code>Section # (or indicate Global)
+  * An explicit list of changes in this format:<code>Section # (or indicate Global)
 OLD:
@@ Line 75: / Line 75: @@
 ===== Sending approval =====
-To approve the RFC for publication, authors should reply to the AUTH48 email stating that they approve the RFC. Please use ‘REPLY ALL’, as all the parties CCed on the message need to see the approval.
+To approve the RFC for publication, all authors should reply to the AUTH48 email stating that they approve the RFC. Please use ‘REPLY ALL’, as all the parties CCed on the message need to see the approval.
 Coauthors are responsible for engaging other parties (e.g., Contributors or Working Group) as necessary before providing approval.