Removed strange sounding wording from the link to the style guide and

added comment about recommended usage of branches

README.md

@@ -30,7 +30,7 @@ both for guidelines on code formatting and git usage.
 And [AngelScript primer][asprimer] for scripting help.
 
 ### C++ Programmers 
-To compile Thrive yourself, you will not only need to follow the [setup instructions][setupguide].
+To compile Thrive yourself, you will need to follow the [setup instructions][setupguide].
 
 Be sure to have a look at the [styleguide][styleguide],
 both for guidelines on code formatting and git usage.

doc/setup_instructions.md

@@ -174,7 +174,8 @@ graphical tool for reviewing the exact lines you have changed, but you
 can also commit on the command line) you can publish them to your fork
 with (assuming you used the master branch, when working with the main
 thrive repository you MUST create a different branch but when working
-with a fork that isn't required):
+with a fork that isn't required, but still strongly recommended as
+making multiple pull requests with one branch is messy):
 
 ```
 git push fork master