From 0333bc172c4bb6c2101ea7d665a33099dd428986 Mon Sep 17 00:00:00 2001 From: Ashley Engelund Date: Fri, 18 Nov 2022 15:39:29 -0800 Subject: [PATCH] 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**