Merge pull request Vonage#86 from prik-k/patch-1

Update README.md

Author: lukeocodes

conversation/README.md

@@ -2,7 +2,7 @@
 
 ## Testing Conversation API Curl scripts
 
-These are some notes on testing the Conversation API using these Curl scripts.
+These are some notes on testing the Conversation API using these `Curl` scripts.
 
 Eventually I would like to write an automated script to do this but for now it's manual.
 
@@ -33,18 +33,18 @@ These are used to test various objects in the Conversation API.
 
 1. Create a Conversation - set the variable `CONVERSATION_ID` in your `config.local.sh` file.
 2. List Conversations - confirm `CONVERSATION_ID` returned is as expected.
-3. Get a Conversation
+3. Get a Conversation.
 4. Update a Conversation - you can change the name of the Conversation for example. Use `get-conversation.sh` to check the change.
-5. Delete a Conversation - then list Conversations again to make sure it has been removed
+5. Delete a Conversation - then list Conversations again to make sure it has been removed fully.
 
 Create a new Conversation before moving on to testing User. Make sure you update `config.local.sh`.
 
 ### User
 
 1. Create a User - set the variable `USER_ID` in your `config.local.sh` file.
-2. List Users 
-3. Get a User
-4. Update a User - then use get-user.sh to make sure the user was updated.
+2. List Users .
+3. Get a User.
+4. Update a User - then use `get-user.sh` to make sure the user was updated.
 5. Get a User Conversations - the user has not been joined to any conversations so this will be an empty array.
 6. Delete a User - list users to confirm empty array is returned.
 
@@ -72,7 +72,7 @@ to test events you will need to join the member into a conversation. To do this
 
 ### Leg
 
-Depending on what other testing you have done on the APP_ID you might
+Depending on what other testing you have done on the `APP_ID` you might
 not have any Legs. The quickest way to create a Leg for testing
 purposes is as follows:
 
@@ -81,7 +81,7 @@ purposes is as follows:
 
 Now that at least one leg has been created:
 
-1. List Legs - make a note of a leg UUID (part of the legs JSON object) and set in your local config.
+1. List Legs - make a note of a leg `UUID` (part of the legs `JSON object`) and set in your local config.
 2. Delete a Leg - Delete a leg and confirm deletion by listing legs.
 
 ---