diff --git a/docs/community/contributing.md b/docs/community/contributing.md index badd821d0..368ab6a6a 100644 --- a/docs/community/contributing.md +++ b/docs/community/contributing.md @@ -372,7 +372,7 @@ Likewise, if users don't know that there is a new feature that you've implemente The documentation has to be updated for users to know that things have been changed and added! If you are adding a new feature, add `(v10.8.0+)` in the title or description. It will be replaced automatically with the current version number when the release happens. -eg: `# Feature Name (v+)` +eg: `# Feature Name (v10.8.0+)` We know it can sometimes be hard to code _and_ write user documentation. diff --git a/packages/mermaid/src/docs/community/contributing.md b/packages/mermaid/src/docs/community/contributing.md index 153fdc6af..7d8aafa4c 100644 --- a/packages/mermaid/src/docs/community/contributing.md +++ b/packages/mermaid/src/docs/community/contributing.md @@ -373,7 +373,7 @@ Likewise, if users don't know that there is a new feature that you've implemente The documentation has to be updated for users to know that things have been changed and added! If you are adding a new feature, add `(v10.8.0+)` in the title or description. It will be replaced automatically with the current version number when the release happens. -eg: `# Feature Name (v+)` +eg: `# Feature Name (v10.8.0+)` We know it can sometimes be hard to code _and_ write user documentation.