Fix typos.
git-svn-id: https://svn.apache.org/repos/asf/maven/plugins/trunk@1229386 13f79535-47bb-0310-9956-ffa450edef68
diff --git a/src/site/apt/tests.apt b/src/site/apt/tests.apt
index f6f94ce..4a1c4eb 100644
--- a/src/site/apt/tests.apt
+++ b/src/site/apt/tests.apt
@@ -26,7 +26,7 @@
EAR Plugin Tests
- This page lists the ear plugin integration tests. Each tests is built on top of a sample project available in
+ This page lists the EAR Plugin integration tests. Each tests is built on top of a sample project available in
the {{{http://svn.apache.org/viewvc/maven/plugins/trunk/maven-ear-plugin/src/test/resources/projects/}svn repository}}.
This structure provides lots of concrete use cases for beginners.
@@ -104,7 +104,7 @@
* project-037: builds an EAR and make sure that ejb-client dependencies are detected and added in the generated application.xml if includeInApplicationXml is set
- * project-038: builds an EAR and make sure that a non-classified dependency with mutiple candidates is detected when specifying the mainArtifactId as classifier
+ * project-038: builds an EAR and make sure that a non-classified dependency with multiple candidates is detected when specifying the mainArtifactId as classifier
* project-039: builds an EAR with a Jboss 4 configuration specifying the loader repository to use
diff --git a/src/site/apt/usage.apt.vm b/src/site/apt/usage.apt.vm
index eff1198..2b90582 100644
--- a/src/site/apt/usage.apt.vm
+++ b/src/site/apt/usage.apt.vm
@@ -34,14 +34,14 @@
* Introduction
- The EAR Plugin allows to generate automatically the deployment descriptor, e.g.
- <<<application.xml>>>. This generation is already customized by the goal's
+ The EAR Plugin allows you to automatically generate the deployment descriptor, e.g.
+ <<<application.xml>>>. This generation is customizable by the goal's
parameters, see {{{./plugin-info.html}the goals description}}.
* Configuring the EAR Plugin
- The configuration of the EAR Plugin is not any different to the configuration
- of the other plugins. The configuration should be similar to:
+ The configuration of the EAR Plugin is not any different from the configuration
+ of any other plugin. The configuration should be similar to:
+-----
<project>
@@ -61,15 +61,15 @@
</project>
+-----
- When configuring the EAR Plugin in your <<<pom.xml>>>, you do not declare any
- <<<\<executions\>>>> elements in it because it is always invoked at least once
+ When configuring the EAR Plugin in your <<<pom.xml>>>, you do not declare an
+ <<<\<executions\>>>> element in it because it is always invoked at least once
during the <<<package>>> phase of an <<<ear>>> project.
* Executing and Generating your EAR Package
The EAR Plugin replaces the JAR Plugin when your project <<<\<packaging\>>>> is
<<<ear>>>. So to generate your EAR package, you need only call the <<<package>>>
- phase like so:
+ phase like this:
+-----
mvn package
@@ -111,7 +111,7 @@
The security settings might be specified under the <<<security>>> parameter.
- The artifact's types that should be unpacked by default can be specified
+ The artifact types that should be unpacked by default can be specified
using the <<<unpackTypes>>> parameter.
The file name mapping to use for artifacts stored in the EAR can be specified
diff --git a/src/site/fml/faq.fml b/src/site/fml/faq.fml
index c5eab92..3e8c4d9 100644
--- a/src/site/fml/faq.fml
+++ b/src/site/fml/faq.fml
@@ -62,12 +62,12 @@
<question>When should one use the modules configuration?</question>
<answer>
<p>
- By default, the EAR plugin generates sensitive defaults for all the JavaEE dependencies it found in the
+ By default, the EAR plugin generates sensible defaults for all the JavaEE dependencies it finds in the
current project. The <em>modules</em> configuration is useful if you need to customize something such as the
bundle location, context root, etc.
</p>
<p>
- Adding a module entry with only the groupId and artifactIf of a dependency is therefore useless.
+ Adding a module entry with only the groupId and artifactId of a dependency is therefore useless.
</p>
</answer>
</faq>
