Grammar, flow, image, next steps

Updated Grammar, flow, etc; brought over image; linked to next steps
(reviewing)

Author: nyeates

CONTRIBUTING.md

@@ -37,7 +37,7 @@ Like the command-line better? *As an alternative, you can utilize git's native c
 
 ## Use Branches When Creating New Patterns
 We develop new patterns in branches with the naming convention:  
-`pattern/[title-of-pattern-here]`.
+`pattern/<title-of-pattern-here>`.
 
 If you are asked to 'Commit directly...' vs 'Create a new branch...'
 
@@ -67,9 +67,6 @@ After this process, it is our turn to drive you through the pattern creation pro
 
 FIXME: The below content is wrong for this section. Content for this section needs to be written, and the below content needs to be integrated elsewhere (it has some useful info).
 
-![branch, commit, pull request, review](assets/img/branchCommitPullReview.png)
-
-The basic steps below can be thought of as *branch*, *commit*, *pull request*, and *review*.
 
 1. [Create an issue](https://github.com/paypal/InnerSourcePatterns/issues) for each new idea, donut or pattern. The issue should:
   * contain a title of the pattern in format ex: ``pattern/badly-named-piles``

meta/technical-git-howto.md

@@ -1,30 +1,33 @@
 # Command-line git steps for creating a new Pattern
 
-If you want to contribute, the workflow is done through branches. You can see the
-available branches of this repository at [the branches URL](https://github.com/paypal/InnerSourcePatterns/branches)
-or by clicking on the 'branches' button on the main page.
-
-Branches and Pull Requests (PR's) are used to bring discussion/review about a specific inner source pattern.
-New patterns should use, as a first approach, the
-[pattern template](meta/pattern-template.md). There are indeed multiple ways to start a discussion:
-* Pull request your branch and the maintainers will receive a notification.
-* Ask directly for comments to some of the maintainers. You can mention them
-using the symbol '@' prior their nickname.
+If you want to contribute a new pattern, the workflow is done through Branches and Pull Requests (PR's). You can see the available branches on [the branches URL](https://github.com/paypal/InnerSourcePatterns/branches/all) and existing PR's on the [Pull Request page](https://github.com/paypal/InnerSourcePatterns/pulls). Branches are meant to separate content, so that multiple people can work all at once. Pull Requests (PR's) are used to bring discussion/review about a specific inner source pattern. 
+
+There are indeed multiple ways to start a discussion:
+
+* Send a Pull Request for your branch and the maintainers will receive a notification.
+* Create an Issue and ask for comments from some of the maintainers. You can mention them using the '@' symbol prior to their github nickname.
 * Add reviewers to the Pull Request on the website - this sends requests to review your work
 
-Please, when starting a new pattern, be aware that this does not exist. You can
-have a look at some of the existing patterns in this repository.
+New patterns should use, as their base, the [pattern template file](https://raw.githubusercontent.com/paypal/InnerSourcePatterns/master/meta/pattern-template.md). 
+
+Please, when starting a new pattern, make sure that it does not already exist. Take a look at some of the [existing patterns in this repository](https://github.com/paypal/InnerSourcePatterns#reviewed-patterns-proven-and-reviewed).
+
+## Overview of steps
+
+![branch, commit, pull request, review](assets/img/branchCommitPullReview.png)
 
-## How can you create a branch?
+The basic steps below can be thought of as *branch*, *commit*, *pull request*, and *review*.
 
-In first place you need to create a branch (no need to ask for permission!).
-For this, let's clone the repository:
+
+## How do you create a branch?
+
+First you need to create a branch (no need to ask for permission!). For this, let's clone the repository:
 
 ```
 $ git clone https://github.com/paypal/InnerSourcePatterns.git
 ```
 
-Then you should see some message similar to the following one:
+Then you should see a message similar to the following one:
 
 ```
 Cloning into 'InnerSourcePatterns'...
@@ -35,8 +38,7 @@ Unpacking objects: 100% (73/73), done.
 Checking connectivity... done.
 ```
 
-This means that you successfully cloned the repository. Then we need to access
-the directory and check that everything is as expected.
+This means that you successfully cloned the repository. Then we need to access the directory and check that everything is as expected.
 
 ```
 $ cd InnerSourcePatterns/
@@ -55,38 +57,38 @@ $ git branch -a
 ```
 
 The command 'git branch' shows you which branch you are currently working within.
-And with 'git branch -a' you see additional branches which are local and remote (on the web).
+And with 'git branch -a' you see additional branches which are local (on desktop) and remote (on the web).
 There is extra information using the command '$ man git branch' in linux based systems.
 
 Next, in order to create a new branch as a way to start creating a new pattern,
 you need to 'checkout' that branch. As a common nomenclature, all of the
-pattern-related branches should start with the keyword 'pattern/'. Thus, a new
+pattern-related branches should start with the keyword `pattern/`. Thus, a new
 branch with a new pattern named as foo should be as follows:
 
 ```
 $ git checkout -b pattern/foo
 ```
 
 You are now in the 'pattern/foo' branch. When you create a new branch, the files 
-in the directory might appear change. Each branch can have slightly different content,
-and that is intentional. If you need to go again to the 'master' branch or another
-branch, you can easily 'checkout' to those as follows:
+in the directory might appear to have changed. Each branch can have slightly different content, and that is intentional. If you need to go back to the 'master' branch or another branch, you can easily 'checkout' to those as follows:
 
 ```
 $ git checkout <branchname>
 ```
 
 ## Adding a new pattern
 
-Let's imagine we want to work a new pattern related to the activities of the
-Ewoks that for some reason gave up hunting. We should choose some initial
-name for this pattern file that could be 'ewoks-do-not-hunt.md'.
+Let's imagine we want to create a new pattern related to the activities of the
+Ewoks - they gave up hunting for some reason. We should choose some initial
+name for this pattern file. We will use 'ewoks-do-not-hunt.md'.
 
 ```
 $ git checkout -b pattern/ewoks-do-not-hunt
 $ touch ewoks-do-not-hunt.md
 ```
 
+You can fill your [markdown](meta/markdown-info.md) file with the [pattern template text](https://raw.githubusercontent.com/paypal/InnerSourcePatterns/master/meta/pattern-template.md) and begin to fill it in with your pattern.
+
 Once our pattern file is ready to go, we need to add the file to the repo and
 commit that change to our new branch.
 
@@ -101,6 +103,6 @@ And we should finally upload that branch and file to the server.
 $ git push origin pattern/ewoks-do-not-hunt
 ```
 
-Then, if you feel the pattern is ready to review, you can start a Pull Request (PR) asking
-to join your new branch to the master branch. To do this, navigate to the github web repo 
-and get into your new branch. You should see a 'Create pull request' button while in your branch.
+Then, if you feel the pattern is ready to be reviewed, you can start a Pull Request (PR) asking to join your new branch to the github master branch. To do this, navigate to the github web repo and get into your new branch. You should see a 'Create pull request' button while in your branch.
+
+PR's are the mechanism we use for our multi-step Review process. See next steps in [Interacting with Pattern Reviews](CONTRIBUTING.md#c-interacting-with-patterns-reviews).