added some references to things, and cleaned up the most recent section

1 files changed, 7 insertions, 6 deletions

diff --git a/writeup/writeup.tex b/writeup/writeup.tex
index 28f35ce..ce67ea3 100644
--- a/writeup/writeup.tex
+++ b/writeup/writeup.tex
@@ -127,7 +127,7 @@ of \textit{hacker culture}, which would become more common into the 80's and 90'
 box \cite{BLUEbox}.
 
 A key figure in \textit{hacker culture}, as previously mentioned, is Richard Stallman. In the 
-early 1980's he left his job at MIT to work full time on the GNU project, which was designed
+ 1980's e lheft his job at MIT to work full time on the GNU project, which was designed
 to be a full recreation of AT\&T's Unix operating system from the ground up in all Free Software. 
 The idea was to allow anyone access to a Unix like machine without paying AT\&T's expensive license 
 fees, and allow any user to view it, redistribute or edit; it was to be the first fully free 
@@ -159,10 +159,11 @@ its Proprietary counterpart.
 \section{How is Free Software developed}
 The process of developing Free Software has changed over time, especially as the internet came to be,
 allowing developers from all across the world to add things. In modern terms the development process is 
-very simple, A developer can look at a piece of code, make changes to a local version of it, where it 
-can then be uploaded to a central online version of the code. This method was popularized version 
-control systems; such as git\cite{GIT}, which is also free software. What these tools allow for is 
-the work of many people to brought together into one single code base.
+very simple, a developer can look at a piece of code, make changes to a local version of it, then it 
+can be uploaded to a central online version of the code, to be checked by lead maintainers, before becoming
+the part of the main version (developers would say creating a local branch and submitting a pull request). 
+This method was popularized version control systems; such as git\cite{GIT}, which is also free software. 
+What these tools allow for is the work of many people to brought together into one single code base.
 
 When code is submitted, it generally gets split into individual chunks (called patches) which each
 have an individual purpose. Each patch added will fix 1 bug or add 1 feature, this leads to a simple
@@ -172,7 +173,7 @@ need to be written, and distributing the work between many developers.
 Without going into too much detail, this is done by merging all contributions into the main code base
 by comparing line numbers in differing versions, this is a fully automated process, managed by your
 version control system. This pattern of development is liked amongst programmers as it allows many 
-to submit code all at once, which is invaluable if your project has enough developers. This method
+to submit code all at once, which is invaluable if your project has many developers. This method
 is also commonly used in Non-free Software, to manage large development teams\cite{NONFREEvcs}.
 
 \section{Comparing Free Software to its proprietary counterparts}