docs: fix spelling in markdown docs

versions-maven-plugin/src/site/markdown/examples/advancing-dependency-versions.md.vm

@@ -79,7 +79,7 @@ mvn versions:use-next-releases -Dincludes=org.codehaus.plexus:plexus-utils
 ```
 
 The `includes` and `excludes` parameters follow the format `groupId:artifactId:type:classifier`.
-Use a comma separated separated list to specify multiple includes.  Wildcards (\*) can also be used to match
+Use a comma separated list to specify multiple includes.  Wildcards (\*) can also be used to match
 multiple values.
 
 This example will match anything with the groupId "org.codehaus.plexus" and anything with the groupId and
@@ -124,11 +124,11 @@ set of dependencies that you need to track on a regular basis, e.g.
 </project>
 ```
 
-By default, both the `project/dependencyManagment` and `project/dependencies` sections will be processed.
+By default, both the `project/dependencyManagement` and `project/dependencies` sections will be processed.
 You can use the `processDependencies` and `processDependencyManagement` parameters to control which sections
 are processed.
 
-This example will only process the `project/dependencyManagment` section of your pom:
+This example will only process the `project/dependencyManagement` section of your pom:
 
 ```sh
 mvn versions:use-next-releases -DprocessDependencies=false

versions-maven-plugin/src/site/markdown/examples/compare-dependencies.md

@@ -31,23 +31,23 @@ should be compared, for example
 mvn versions:compare-dependencies -DremotePom=org.foo:bom-pom:1.0
 ```
 
-By default the list of dependency differences will be output to the command line.  This can be
+By default, the list of dependency differences will be output to the command line.  This can be
 written to a file using the "reportOutputFile" parameter.
 
 ```sh
 mvn versions:compare-dependencies -DremotePom=org.foo:bom-pom:1.0 -DreportOutputFile=${project.build.directory}/depDiffs.txt
 ```
 
 The plugin can also automatically update the dependencies of the current project to match
-the remote project using the "updateDependencies" parameter.  By default this is turned off.
+the remote project using the "updateDependencies" parameter.  By default, this is turned off.
 
 ```sh
 mvn versions:compare-dependencies -DremotePom=org.foo:bom-pom:1.0 -DupdateDependencies=true
 ```
 
 In addition to that, any property defined in the current project that represent the version
 of one of several artifacts can be updated to match the remote project using the "updatePropertyVersions"
-parameter. By default this is turned off.
+parameter. By default, this is turned off.
 
 ```sh
 mvn versions:compare-dependencies -DremotePom=org.foo:bom-pom:1.0 -updatePropertyVersions=true

versions-maven-plugin/src/site/markdown/examples/display-property-updates.md

@@ -22,7 +22,7 @@ under the License.
 # Checking for new property-linked updates
 
 The `display-property-updates` goal will check all the properties in your project and display a list
-of those properties which are used to control versions of dependencies, plugins and plugin dependencies and
+of those properties which are used to control versions of dependencies, plugins and plugin dependencies, and
 it will detail which properties have newer versions available.
 
 Here are some examples of what this looks like:

versions-maven-plugin/src/site/markdown/examples/resolve-ranges.md

@@ -89,7 +89,7 @@ mvn versions:resolve-ranges -Dincludes=org.codehaus.plexus:plexus-utils
 ```
 
 The `includes` and `excludes` parameters follow the format `groupId:artifactId:type:classifier`.
-Use a comma separated separated list to specify multiple includes.  Wildcards (*) can also be used to match
+Use a comma separated list to specify multiple includes.  Wildcards (*) can also be used to match
 multiple values.
 
 This example will match anything with the groupId "org.codehaus.plexus" and anything with the groupId and

versions-maven-plugin/src/site/markdown/examples/setaggregator.md

@@ -94,7 +94,7 @@ And two other modules first `module-a2` which looks like this:
 </project>
 ```
 
-An finally the module `module-a3` which looks like this:
+And finally the module `module-a3` which looks like this:
 
 ```xml
 <?xml version="1.0" encoding="UTF-8"?>
@@ -185,7 +185,7 @@ mvn versions:set -DnewVersion=3.6.0 -DoldVersion=* -DgroupId=* -DartifactId=*
 
 This is needed otherwise the filter for the versions (via `-DoldVersion=*`) would have
 filtered out that module cause it has a different version than the rest of modules.
-Furthermore you need to add the `-DgroupId=*` and `-DartifactId=*` otherwise
+Furthermore, you need to add the `-DgroupId=*` and `-DartifactId=*` otherwise
 the `separate-module` will also filtered out based on the differences in groupId
 and artifactId.
 

versions-maven-plugin/src/site/markdown/examples/unlock-snapshots.md

@@ -28,7 +28,7 @@ release version, but if you need a short term semi-reproducible build, locked -S
 useful hack.
 
 If your pom has specified locked snapshot versions (these will end with the form -YYYYMMDD.HHMMSS-NNN) for certain
-ependencies:
+dependencies:
 
 ```xml
 <dependencies>
@@ -72,7 +72,7 @@ mvn versions:unlock-snapshots -Dincludes=org.codehaus.plexus:plexus-utils
 ```
 
 The `includes` and `excludes` parameters follow the format `groupId:artifactId:type:classifier`.
-Use a comma separated separated list to specify multiple includes.  Wildcards (*) can also be used to match
+Use a comma separated list to specify multiple includes.  Wildcards (*) can also be used to match
 multiple values.
 
 This example will match anything with the groupId "org.codehaus.plexus" and anything with the groupId and

versions-maven-plugin/src/site/markdown/examples/update-properties.md.vm

@@ -328,7 +328,7 @@ snapshots are *never* resolved,
 ## Restricting the properties to be updated using includes / excludes
 
 The **includes** and **excludes` parameters follow the format `groupId:artifactId:type:classifier`.
-Use a comma separated separated list to specify multiple includes.  Wildcards (*) can also be used to match
+Use a comma separated list to specify multiple includes.  Wildcards (*) can also be used to match
 multiple values.
 
 This example will match anything with the groupId "org.codehaus.plexus" and anything with the groupId and

versions-maven-plugin/src/site/markdown/examples/use-releases.md

@@ -67,7 +67,7 @@ mvn versions:use-releases -Dincludes=org.codehaus.plexus:plexus-utils
 ```
 
 The `includes` and `excludes` parameters follow the format `groupId:artifactId:type:classifier`.
-Use a comma separated separated list to specify multiple includes.  Wildcards (*) can also be used to match
+Use a comma separated list to specify multiple includes.  Wildcards (*) can also be used to match
 multiple values.
 
 This example will match anything with the groupId "org.codehaus.plexus" and anything with the groupId and

versions-maven-plugin/src/site/markdown/index.md

@@ -46,7 +46,7 @@ associated artifacts.
 of a project so the version matches the version of the current project. For example, if you have an aggregator pom
 that is also the parent for the projects that it aggregates and the children and parent versions get out of sync, this
 mojo can help fix the versions of the child modules. (Note you may need to invoke Maven with the -N option in order to
-run this goal if your project is broken so badly that it cannot build because of the version mis-match).
+run this goal if your project is broken so badly that it cannot build because of the version mismatch).
 * [versions:lock-snapshots](./lock-snapshots-mojo.html) searches the pom for all -SNAPSHOT versions and replaces them
 with the current timestamp version of that -SNAPSHOT, e.g. -20090327.172306-4
 * [versions:unlock-snapshots](./unlock-snapshots-mojo.html) searches the pom for all timestamp locked snapshot versions