Apply suggestions from code review

Co-authored-by: Matthew Michel <106704043+mmichel11@users.noreply.github.com>
oneapi-src · Oct 2, 2024 · d9613fe · d9613fe
1 parent 1ffa633
commit d9613fe
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/rfcs/archived/README.md b/rfcs/archived/README.md
@@ -5,7 +5,7 @@ two reasons:
 
 1. The document describes a feature or extension that has been deprecated and 
 then removed.
-2. The document describes a proposed feature or extension that have
+2. The document describes a proposed feature or extension that has
 not (ultimately) become a fully supported feature. 
 
 Design documents that appear in the `rfcs/archived` folder should describe a 

diff --git a/rfcs/template.md b/rfcs/template.md
@@ -40,7 +40,7 @@ Pay close attention to the following aspects of the library:
 
 Include short explanation and links to the related proposals, if any.
 Sub-proposals could be organized as separate standalone RFCs, but this is
-not mandatory. If the related change is insignificant or doesn't make any sense
+not mandatory. If the related change is insignificant or does not make any sense
 without the original proposal, describe it in the main RFC.
 
 Some other common subsections could be: