From 1caa3cbecc0d1bf719b61fa09d2bbc3ea422a166 Mon Sep 17 00:00:00 2001
From: Jimmy Debe <91767824+jimstir@users.noreply.github.com>
Date: Sat, 13 Jan 2024 22:49:42 -0500
Subject: [PATCH] Update README.md

---
 content/docs/rfcs/1/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/docs/rfcs/1/README.md b/content/docs/rfcs/1/README.md
index 5abadac5..a0362245 100644
--- a/content/docs/rfcs/1/README.md
+++ b/content/docs/rfcs/1/README.md
@@ -23,7 +23,7 @@ It is equivalent except for some areas:
 - recommending the use of a permissive licenses, such as CC0 (with the exception of this document);
 - miscellaneous metadata, editor, and format/link updates;
 - more inheritance from the [IETF Standards Process][https://www.rfc-editor.org/rfc/rfc2026.txt],
-  e.g. using RFC categories: Standards Track, Informational, and Best Common Practice;
+  e.g. using RFC categories: Standards Track, Informational, Best Common Practice, Experimental;
 - standards track specifications SHOULD follow a specific structure that both streamlines editing,
   and helps implementers to quickly comprehend the specification
 - specifications MUST feature a header providing specific meta information