From 9e980c0c0b39596ae5f5dbe053aeacc4628edb20 Mon Sep 17 00:00:00 2001 From: Josh Moore Date: Fri, 30 Aug 2024 17:47:44 +0200 Subject: [PATCH] Add missing word --- rfc/1/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rfc/1/index.md b/rfc/1/index.md index 69c390bd..4ee09ead 100644 --- a/rfc/1/index.md +++ b/rfc/1/index.md @@ -408,7 +408,7 @@ The IETF RFC process disallows edits to published RFCs. (In the extreme case, a Though this decision may be reviewed in the future, RFCs MAY be edited, but **Editors** SHOULD limit modifications to _adopted_ RFCs only for: - clarification: additional text and examples which simplify the implementation of specifications are welcome; - deprecation: where sections are no longer accurate and especially when they have been replaced by a new RFC, the existing text can be marked and a link to the updated information provided; -- and extension: references to new RFCs can be added throughout an existing to provide simpler reading for **Implementers**. +- and extension: references to new RFCs can be added throughout an existing RFC to provide simpler reading for **Implementers**. In writing RFCs, **Authors** SHOULD attempt to clearly identify sections which may be deprecated or extended in the future.