From 71d2175e19370317e268f5f7232bdfcd0d8e9e89 Mon Sep 17 00:00:00 2001 From: Ashley Engelund Date: Fri, 18 Nov 2022 15:38:52 -0800 Subject: [PATCH 1/2] questions? search in... capitalize Search, + closed issues Co-authored-by: Sidharth Vinod --- packages/mermaid/src/docs/community/development.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/packages/mermaid/src/docs/community/development.md b/packages/mermaid/src/docs/community/development.md index 2779141de..0618040df 100644 --- a/packages/mermaid/src/docs/community/development.md +++ b/packages/mermaid/src/docs/community/development.md @@ -274,8 +274,9 @@ To edit Docs on GitHub: #### First search to see if someone has already asked (and hopefully been answered) or suggested the same thing. -- search in the Discussions -- search in the open Issues +- Search in Discussions +- Search in open Issues +- Search in closed Issues If you find an open issue or discussion thread that is similar to your question but isn't answered, you can let us know that you are also interested in it. **_[TODO: describe upvoting]_** From 0333bc172c4bb6c2101ea7d665a33099dd428986 Mon Sep 17 00:00:00 2001 From: Ashley Engelund Date: Fri, 18 Nov 2022 15:39:29 -0800 Subject: [PATCH 2/2] spelling: description; .. help us keep release notes organized Co-authored-by: Sidharth Vinod --- packages/mermaid/src/docs/community/development.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/mermaid/src/docs/community/development.md b/packages/mermaid/src/docs/community/development.md index 0618040df..6c086ca6f 100644 --- a/packages/mermaid/src/docs/community/development.md +++ b/packages/mermaid/src/docs/community/development.md @@ -110,7 +110,7 @@ We use the follow naming convention for branches: - followed by an _underscore_ ('\_') - followed by a short text description (but use dashes ('-') or underscores ('\_') instead of spaces) -If your work is specific to a single diagram type, it is a good idea to put the diagram type at the start of the dscription. This will help use keep release notes organized: it will help us keep changes for a diagram type together. +If your work is specific to a single diagram type, it is a good idea to put the diagram type at the start of the description. This will help us keep release notes organized: it will help us keep changes for a diagram type together. **Ex: A new feature described in issue 2945 that adds a new arrow type called 'florbs' to state diagrams**