Merge pull request #368 from michaelmior/fix-typo

Fix typo in Javadoc/documentation

docs/releases/4.1/execute-commands-mojo.html

@@ -109,7 +109,7 @@ <h2 id="wildflyexecute-commands"><a name="wildfly:execute-commands"></a>wildfly:
  <p>org.wildfly.plugins:wildfly-maven-plugin:4.1.1.Final:execute-commands</p>
  <p><b>Description</b>:</p>
  <div>
-  Execute commands to the running WildFly Application Server. Commands should be formatted in the same manor CLI commands are formatted. Executing commands in a batch will rollback all changes if one command fails. 
+  Execute commands to the running WildFly Application Server. Commands should be formatted in the same manner CLI commands are formatted. Executing commands in a batch will rollback all changes if one command fails. 
   <div>
    <pre class="border shadow rounded">     &lt;batch&gt;true&lt;/batch&gt;
      &lt;fail-on-error&gt;false&lt;/fail-on-error&gt;

docs/releases/4.1/plugin-info.html

@@ -128,15 +128,15 @@ <h2 id="Plugin-Documentation"><a name="Plugin_Documentation"></a>Plugin Document
    </tr>
    <tr>
     <td><a href="deploy-only-mojo.html">wildfly:deploy-only</a></td>
-    <td>Deploys only the application to the WildFly Application Server without first invoking the the execution of the lifecycle phase 'package' prior to executing itself. If <code>force</code> is set to <code>true</code>, the server is queried to see if the application already exists. If the application already exists, the application is redeployed instead of deployed. If the application does not exist the application is deployed as normal. If <code>force</code> is set to <code>false</code> and the application has already been deployed to the server, an error will occur and the deployment will fail.</td>
+    <td>Deploys only the application to the WildFly Application Server without first invoking the the Execution of the lifecycle phase 'package' prior to executing itself. If <code>force</code> is set to <code>true</code>, the server is queried to see if the application already exists. If the application already exists, the application is redeployed instead of deployed. If the application does not exist the application is deployed as normal. If <code>force</code> is set to <code>false</code> and the application has already been deployed to the server, an error will occur and the deployment will fail.</td>
    </tr>
    <tr>
     <td><a href="dev-mojo.html">wildfly:dev</a></td>
     <td>Starts a standalone instance of WildFly and deploys the application to the server. The deployment type myst be a WAR. Once the server is running, the source directories are monitored for changes. If required the sources will be compiled and the deployment may be redeployed. <p>Note that changes to the POM file are not monitored. If changes are made the POM file, the process will need to be terminated and restarted.</p></td>
    </tr>
    <tr>
     <td><a href="execute-commands-mojo.html">wildfly:execute-commands</a></td>
-    <td>Execute commands to the running WildFly Application Server. Commands should be formatted in the same manor CLI commands are formatted. Executing commands in a batch will rollback all changes if one command fails. <pre class="border shadow rounded">     &lt;batch&gt;true&lt;/batch&gt;
+    <td>Execute commands to the running WildFly Application Server. Commands should be formatted in the same manner CLI commands are formatted. Executing commands in a batch will rollback all changes if one command fails. <pre class="border shadow rounded">     &lt;batch&gt;true&lt;/batch&gt;
      &lt;fail-on-error&gt;false&lt;/fail-on-error&gt;
      &lt;commands&gt;
          &lt;command&gt;/subsystem=logging/console=CONSOLE:write-attribute(name=level,value=DEBUG)&lt;/command&gt;

docs/releases/4.2/execute-commands-mojo.html

@@ -109,7 +109,7 @@ <h2 id="wildflyexecute-commands"><a name="wildfly:execute-commands"></a>wildfly:
  <p>org.wildfly.plugins:wildfly-maven-plugin:4.2.0.Final:execute-commands</p>
  <p><b>Description</b>:</p>
  <div>
-  Execute commands to the running WildFly Application Server. Commands should be formatted in the same manor CLI commands are formatted. Executing commands in a batch will rollback all changes if one command fails. 
+  Execute commands to the running WildFly Application Server. Commands should be formatted in the same manner CLI commands are formatted. Executing commands in a batch will rollback all changes if one command fails. 
   <div>
    <pre class="border shadow rounded">     &lt;batch&gt;true&lt;/batch&gt;
      &lt;fail-on-error&gt;false&lt;/fail-on-error&gt;

docs/releases/4.2/plugin-info.html

@@ -136,7 +136,7 @@ <h2 id="Plugin-Documentation"><a name="Plugin_Documentation"></a>Plugin Document
    </tr>
    <tr>
     <td><a href="execute-commands-mojo.html">wildfly:execute-commands</a></td>
-    <td>Execute commands to the running WildFly Application Server. Commands should be formatted in the same manor CLI commands are formatted. Executing commands in a batch will rollback all changes if one command fails. <pre class="border shadow rounded">     &lt;batch&gt;true&lt;/batch&gt;
+    <td>Execute commands to the running WildFly Application Server. Commands should be formatted in the same manner CLI commands are formatted. Executing commands in a batch will rollback all changes if one command fails. <pre class="border shadow rounded">     &lt;batch&gt;true&lt;/batch&gt;
      &lt;fail-on-error&gt;false&lt;/fail-on-error&gt;
      &lt;commands&gt;
          &lt;command&gt;/subsystem=logging/console=CONSOLE:write-attribute(name=level,value=DEBUG)&lt;/command&gt;

plugin/src/main/java/org/wildfly/plugin/cli/ExecuteCommandsMojo.java

@@ -52,7 +52,7 @@
 /**
  * Execute commands to the running WildFly Application Server.
  * <p/>
- * Commands should be formatted in the same manor CLI commands are formatted.
+ * Commands should be formatted in the same manner CLI commands are formatted.
  * <p/>
  * Executing commands in a batch will rollback all changes if one command fails.
  *