From 5acd29be0fc91073ebd0fb700211103ab5271ff5 Mon Sep 17 00:00:00 2001 From: Arseny Kapoulkine Date: Mon, 3 May 2021 13:37:12 -0700 Subject: [PATCH] Naming --- rfcs/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rfcs/README.md b/rfcs/README.md index 0bf62e23..f98c6e3b 100644 --- a/rfcs/README.md +++ b/rfcs/README.md @@ -25,7 +25,7 @@ Since reversing these decisions is incredibly costly and can be impossible due t Process === -To open an RFC, a Pull Request must be opened which creates a new Markdown file in rfcs/ folder. The RFCs should follow the template `rfcs/TEMPLATE.md`, and should have a file name that is a short human readable description of the feature (using lowercase alphanumeric characters and dashes only). +To open an RFC, a Pull Request must be opened which creates a new Markdown file in `rfcs/` folder. The RFCs should follow the template `rfcs/TEMPLATE.md`, and should have a file name that is a short human readable description of the feature (using lowercase alphanumeric characters and dashes only). Try using the general area of the RFC as a prefix, e.g. `syntax-generic-functions.md` or `function-debug-info.md`. The PR will hav > Note: we currently don't accept community contributions for RFCs, although this will likely change in the future.