### Eclipse Workspace Patch 1.0
#P trunk-arquillian
Index: doc/reference/src/main/docbook/en-US/examples.xml
===================================================================
--- doc/reference/src/main/docbook/en-US/examples.xml	(revision 4254)
+++ doc/reference/src/main/docbook/en-US/examples.xml	(working copy)
@@ -92,7 +92,7 @@
    </para>
 
    <para>
-      Asssuming you have JBoss AS started from running the tests on the command line, you can now execute the tests.
+      Assuming you have JBoss AS started from running the tests on the command line, you can now execute the tests.
       Right click on the InjectionTestCase.java file in the Package Explorer and select Run As... > JUnit Test
       or Run As... > TestNG Test depending on which unit testing framework the test is using.
    </para>
Index: doc/reference/src/main/docbook/en-US/execution.xml
===================================================================
--- doc/reference/src/main/docbook/en-US/execution.xml	(revision 4254)
+++ doc/reference/src/main/docbook/en-US/execution.xml	(working copy)
@@ -114,7 +114,7 @@
          Arquillian delegates to an SPI (service provider interface) to handle starting and stopping the server and
          deploying and undeploying archives. In this case, the SPI is the interface
          <literal>org.jboss.arquillian.spi.DeployableContainer</literal>. If you recall from the getting started
-         section, we included an Arquillian library according to the target container we wanted to us. That library
+         section, we included an Arquillian library according to the target container we wanted to use. That library
          contains an implementation of this interface, thus controlling how Arquillian handles deployment. If you wanted to
          introduce support for another container in Arquillian, you would simply provide an implementation of this
          interface.
Index: doc/reference/src/main/docbook/en-US/enrichment.xml
===================================================================
--- doc/reference/src/main/docbook/en-US/enrichment.xml	(revision 4254)
+++ doc/reference/src/main/docbook/en-US/enrichment.xml	(working copy)
@@ -8,7 +8,7 @@
       When you use a unit testing framework like JUnit or TestNG, your test case lives in a world on its own. That
       makes integration testing pretty difficult because it means the environment in which the business logic
       executes must be self-contained within the scope of the test case (whether at the suite, class or method
-      level). The onus of setting up this environment in the test falls on the developer's shoulders.
+      level). The bonus of setting up this environment in the test falls on the developer's shoulders.
    </para>
 
    <para>