Merge pull request #4 from open-horizon-services/Issue-3-README

Issue 3: README spell check

README.md

@@ -68,7 +68,7 @@ Note: testing the Minecraft server currently requires you to own a copy of the M
 
 To manually run a minecraft server locally as a test, enter `make`.  Currently to test if the server is working, you will have to manually open your Minecraft client and attempt to connect.  It will likely take a few minutes for the server to start up and prepare the world.  Running `make attach` will connect you to a prompt running inside the container, and you can end that session by entering `stop`.  When you are done, run `make stop` in the terminal to end the test.
 
-To create [the service definition](https://github.com/open-horizon/examples/blob/master/edge/services/helloworld/CreateService.md#build-publish-your-hw), publish it to the hub, and then form an agreement to download and run a Minecraft server, enter `make publish`.  When installation is complete and an agreement has been formed, exit the watch command with Control-C. 
+To create [the service definition](https://github.com/open-horizon/examples/blob/master/edge/services/helloworld/CreateService.md#build-publish-your-hw), publish it to the hub, and then form an agreement to download and run a Minecraft server, enter `make publish`.  When installation is complete and an agreement has been formed, exit the watch command with Control-C.
 
 ## Advanced details
 
@@ -78,7 +78,7 @@ The Makefile includes several targets to assist you in inspecting what is happen
 
 `make log` to see both the event logs and the service logs.
 
-`make deploy-check` to see if the properties and contstraints that you've configured match each other to potentially form an agreement.
+`make deploy-check` to see if the properties and constraints that you've configured match each other to potentially form an agreement.
 
 `make test` to see if the web server is responding.
 
@@ -107,4 +107,4 @@ The Makefile includes several targets to assist you in inspecting what is happen
 * `publish` - Publish the service def, service policy, deployment policy, and then register your agent
 * `agent-stop` - unregister your agent with the hub, halting all agreements and stopping containers
 * `deploy-check` - confirm that a registered agent is compatible with the service and deployment
-* `log` - check the agent event logs
+* `log` - check the agent event logs