Fix errors, typos, grammar, and broken link in site documentation

src/site/apt/examples/rapid-testing-jetty6-plugin.apt

@@ -72,4 +72,4 @@ Rapid Testing Using the Jetty Plugin
 
  The command will block with Jetty listening on port 8080.
 
- Check the {{{http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin}Jetty Plugin documentation}} for more details.
+  Check the {{{https://jetty.org/docs/jetty/12/programming-guide/maven-jetty/jetty-maven-plugin.html}Jetty Plugin documentation}} for more details.

src/site/apt/examples/war-manifest-guide.apt.vm

@@ -66,7 +66,7 @@ WAR Manifest Customization
   Now, you can control which dependencies are included in <<<WEB-INF/lib>>> and in the manifest classpath by following
   these examples.  Maven will follow the transitive dependency tree until it gets to artifacts scoped as "provided".
 
-  <<Note:>> No way is shown how to include a dependency in <<<WEB-INF/lib>>> but not in the manifest classpath.
+  <<Note:>> No example is shown for including a dependency in <<<WEB-INF/lib>>> while excluding it from the manifest classpath.
 
 +--------------------+
 <project>

src/site/apt/index.apt.vm

@@ -38,11 +38,11 @@ ${project.name}
    <<<package>>> phase for projects with a packaging type of <<<war>>>. 
    It builds a WAR file.
 
- * {{{./exploded-mojo.html}war:exploded}} is generally used to speed up 
-   testing during the developement phase by creating an exploded webapp 
+ * {{{./exploded-mojo.html}war:exploded}} speeds up 
+   testing during the development phase by creating an exploded webapp 
    in a specified directory.
 
- * {{{./inplace-mojo.html}war:inplace}} another variation of <<<war:explode>>> 
+  * {{{./inplace-mojo.html}war:inplace}} is another variation of <<<war:exploded>>> 
    where the webapp is instead generated in the web application source directory, 
    which is <<<src/main/webapp>>> by default.
 

src/site/apt/overlays.apt.vm

@@ -157,7 +157,7 @@ documentedprojectdependency-1.0-SNAPSHOT.war
   configure. Default value is: <<<war>>>.
 
   * <<classifier>> - the classifier of the overlay artifact you want to
-  configure if multiple artifacts matches the groupId/artifactId.
+  configure if multiple artifacts match the groupId/artifactId.
 
   * <<includes>> - the files to include. By default, all files are included.
 
@@ -255,8 +255,8 @@ documentedprojectdependency-1.0-SNAPSHOT.war
   since they have not been configured in the <<<\<overlays\>>>> element.
 
   To perform an even more fine grained overwriting policy, overlays can be packaged multiple times
-  with different includes/excludes. For instance if the <<<index.jsp>>> file of the
-  overlay <<<my-webapp>>> <<must>> be set in the webapp but other files can be controlled the
+  with different includes/excludes. For example, if the <<<index.jsp>>> file of the
+  overlay <<<my-webapp>>> <<must>> be set in the webapp but other files can be controlled in the
   regular way, define two overlay configurations for <<<my-webapp>>>:
 
 +-----------------+

src/site/apt/usage.apt.vm

@@ -129,7 +129,7 @@ documentedproject-1.0-SNAPSHOT.war
 
 *Invocation of <<<war:exploded>>> goal
 
- To speed up testing during the developement phase, <<<war:explode>>> can be used to generate the WAR in exploded
+  To speed up testing during the development phase, <<<war:exploded>>> can generate the WAR in exploded
  form.
  Use the same project as above and invoke: