commit 3618e45917eb15f3cdbff01c32f08ae12f21aaa7
parent 0a42851f63dceb70983d7df74f4b25d1b989c1de
Author: Pedro Rodrigues <35636428+pedrodsrodrigues@users.noreply.github.com>
Date: Mon, 9 Jan 2023 18:05:05 +0000
Fix typo in CONTRIBUTING.md (#2831)
Fix typo when specifying the "/doc/specs" directory, in the "CONTRIBUTING.md" file.
Diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -91,7 +91,7 @@ Specs will be managed in a very similar manner as code contributions so please f
To write/contribute to a spec: fork, branch and commit via PRs, as you would with any code changes.
-Specs are written in markdown, stored under the `/doc/spec` folder and named `[issue id] - [spec description].md`.
+Specs are written in markdown, stored under the `/doc/specs` folder and named `[issue id] - [spec description].md`.
👉 **It is important to follow the spec templates and complete the requested information**. The available spec templates will help ensure that specs contain the minimum information & decisions necessary to permit development to begin. In particular, specs require you to confirm that you've already discussed the issue/idea with the team in an issue and that you provide the issue ID for reference.
