docs: add multiple scope support info conventional-changelog#701

Author: escapedcat

README.md

@@ -43,7 +43,7 @@ commitlint checks if your commit messages meet the [conventional commit format](
 In general the pattern mostly looks like this:
 
 ```sh
-type(scope?): subject  #scope is optional
+type(scope?): subject  #scope is optional; multiple scopes are supported (current delimiter options: "/", "\" and ",")
 ```
 
 Real world examples can look like this:

docs/concepts-commit-conventions.md

@@ -1,6 +1,6 @@
 # Concept: Commit conventions
 
-Commit conventions allow your team to add more semantic meaning to your git history. This e.g. includes `type`, `scope` or `breaking changes`.
+[Commit conventions](https://www.conventionalcommits.org/) allow your team to add more semantic meaning to your git history. This e.g. includes `type`, `scope` or `breaking changes`.
 
 With this additional information tools can derive useful human-readable information for releases of your project. Some examples are
 
@@ -15,3 +15,12 @@ type(scope?): subject
 body?
 footer?
 ```
+
+## Multiple scopes
+
+Commitlint supports multiple scopes.  
+Current delimiter options are:
+
+- "/"
+- "\"
+- ","