Minor typos

Author: Reza Rahman

README.md

@@ -3,7 +3,7 @@ Testing Java EE Applications on WebLogic 12.1.3 Using Arquillian
 This application demonstrates how Java EE applications can be effectively 
 tested using Arquillian on WebLogic 12.1.3. The application contains a 
 set of JUnit tests that you should examine. The tests will be run as part 
-of the Maven build. The tests require a locally running instance of 
+of the Maven build. The tests require a running instance of 
 WebLogic (please see setup instructions).
 
 WebLogic 12.1.3 supports Java EE 6 and some key Java EE 7 APIs - 
@@ -27,18 +27,18 @@ Setup
   approach we used. As a result, however, you will need to manually create a
   data source for the demo application. The data source is expected to be bound 
   to 'jdbc/ActionBazaarDB'. We used embedded Derby but any underlying database
-  should work. If helpful, a sample source definition is provided 
+  should work. If helpful, a sample WebLogic data source definition is provided 
   [here](ActionBazaarDB-jdbc.xml).
-* Please download this repository. You can use GitHub or just the simple zip
+* Please download this repository. You can use Git or just the simple zip
   download.
 * The demo is just a simple Maven project under the [actionbazaar](actionbazaar)
   directory. You should be able to open it up in any Maven capable IDE, we used
   NetBeans.
 * If desired setup WebLogic in your IDE. This is what we tested.
 * The tests in the Maven build are executed against a running WebLogic instance.
   You will need to configure 
-  [this file] (actionbazaar\src\test\resources\arquillian.xml) with the details
-  of our running WebLogic instance (you could run the instance via the IDE).
+  [this file] (actionbazaar/src/test/resources/arquillian.xml) with the details
+  of your running WebLogic instance (you could run the instance via the IDE).
   For details on configuring WebLogic for Arquillian, look 
   [here] (https://docs.jboss.org/author/display/ARQ/WLS+12.1+-+Remote).
 * If desired, you can deploy and run the application itself. We did this both