Update Git_workflow_exercises.md

re-organize

Author: DanteDT

Diff for: docs/guides/Git_workflow_exercises.md

@@ -2,26 +2,21 @@
 
 To get setup as a PhUSE CS contributor, see [Contributor_setup.md](https://github.com/phuse-org/phuse-scripts/blob/master/docs/guides/Contributor_Setup.md)
 
-Relevant roles for phuse-org/phuse-scripts are:
-  1. Admin
-  2. Developer
-  3. ? [our repo teams](https://github.com/phuse-org/phuse-scripts/settings/collaboration) -- Owner? Admin? Is this the right setup?
-
 ### Objective
 Script GitHub workflow exercises for CSS 2016.
 
-### Git workflow tutorials
-
-  * [Atlassian Git Workflows](http://www.atlassian.com/git/tutorials/comparing-workflows)
-  * [Learn git on Codecademy](http://www.codecademy.com/learn/learn-git)
-
 ### GitHub Roles
 
 [GitHub article on Repository Permission Levels](https://help.github.com/articles/repository-permission-levels-for-an-organization/)
 
   1. phuse-or/phuse-scripts Maintainers: can change master code
   2. GitHub Contributors: can create "pull request" from their own branch, for the Maintainers to review
 
+Relevant roles for phuse-org/phuse-scripts?
+  1. Admin
+  2. Developer
+  3. ? [our repo teams](https://github.com/phuse-org/phuse-scripts/settings/collaboration) -- Owner? Admin? Is this the right setup?
+
 #### phuse-or/phuse-scripts Setup
 
   * Master branch is always "production ready"
@@ -43,3 +38,8 @@ Script GitHub workflow exercises for CSS 2016.
     3. "pull" changes from master branch
     4. resolve any conflicts
     5. "pull request" ... screenshots
+
+### Git workflow tutorials
+
+  * [Atlassian Git Workflows](http://www.atlassian.com/git/tutorials/comparing-workflows)
+  * [Learn git on Codecademy](http://www.codecademy.com/learn/learn-git)