From df01dad8d600966cc4a4ec05a5da34dcf34a49a2 Mon Sep 17 00:00:00 2001
From: Alexander <alexander.r.ambrose@gmail.com>
Date: Mon, 23 Jul 2012 22:49:33 -0400
Subject: [PATCH] Proofread How To Read This Resource & Sudo Language

---
 .../1.2 - How To Read This Resource.tex       | 13 +++++----
 2 - Getting Started/1.3 - Sudo Language.tex   | 27 ++++++++-----------
 2 files changed, 17 insertions(+), 23 deletions(-)

diff --git a/2 - Getting Started/1.2 - How To Read This Resource.tex b/2 - Getting Started/1.2 - How To Read This Resource.tex
index 5a7dc22..9ff5302 100644
--- a/2 - Getting Started/1.2 - How To Read This Resource.tex	
+++ b/2 - Getting Started/1.2 - How To Read This Resource.tex	
@@ -1,12 +1,11 @@
-This resource is going to be laid out a little weird, more so for those who have already had some programming background.
+This resource is going to be laid out a little weird, more so for those who have already have some programming background.
 \par
 
-For those who are new to programming I strongly suggest reading through Chapters 3 and 4 thoroughly before continuing with the
-rest of the resource.
-Those two chapters contain all of the core concepts needed in order to understand some of the higher level concepts
-presented with Data Structures and Algorithms.
-Once you have completed chapters 3 and 4 please feel free to jump around a little between sections presented in chapters 5 and 6 as
-some data structures or algorithms might interest you more than others.
+For those who are new to programming, I strongly suggest reading through Chapters 3 and 4 thoroughly before continuing with the
+rest of this resource as they contain all of the core concepts needed in order to understand some of the higher level concepts
+presented in Data Structures and Algorithms.
+Once you have completed chapters 3 and 4 please feel free to jump around between sections presented in chapters 5 and 6 as
+certain data structures or algorithms might interest you more than others.
 
 \subsection{Keywords}
 
diff --git a/2 - Getting Started/1.3 - Sudo Language.tex b/2 - Getting Started/1.3 - Sudo Language.tex
index 4267972..eac5b0b 100644
--- a/2 - Getting Started/1.3 - Sudo Language.tex	
+++ b/2 - Getting Started/1.3 - Sudo Language.tex	
@@ -3,10 +3,9 @@ The concept behind a sudo language is to be able to present programming concepts
 language agnostic form so that the concepts can be translated to your language of choice.
 \par
 
-So it is great that you have chosen lanauge X to use throughout this resource, but how is the sudo lanauge going to help you out?
-Well, lets look at two examples and I will show their implementation in a few different languages.
-Hopefully this will help you be able to understand how the language should be tanslates (especially if your language of choice
-is one that I use).
+It is great that you have chosen lanauge X to use throughout this resource, but how is the sudo lanauge going to help you out?
+Well, let's look at two examples and I will show their implementation in a few different languages.
+Hopefully this will help you to understand how the language should be tanslated to others (especially if your language of choice is one that I use).
 
 \subsection{Example 1}
 
@@ -35,8 +34,7 @@ For this example lets break it down line by line to make sure we know exactly wh
     \end{enumerate}
 \end{enumerate}
 
-As far as programming goes this is a fairly simple process but lets try and translate this example to a
-few different languages to see how it is done.
+As far as programming goes this is a fairly simple process but let's try to translate this example to a few different languages to see how it is done.
 
 \begin{lstlisting}[language=php,caption={Example 1 - PHP}]
 <?php
@@ -90,15 +88,13 @@ class Example1{
 }
 \end{lstlisting}
 
-Notice that all of the actual examples end up looking the same?
-That is the point of using the sudo language, so that we can discuss the core concepts of the lesson
-at hand and then those concepts can be directly applied to any language of choice.
+Notice that all of the actual examples end up looking about the same? This is the point of using the sudo language. This way I can discuss the core concepts of the lesson at hand and then those concepts can be directly applied to any language of your choice.
 \par
 
-Also, notice the Python implementation, it is almost line for line, word for word identical to the sudo language example.
+Also, notice the Python implementation, it is almost line for line, word for word identical to the sudo language example. If you would like to choose a language closest to the sudo language, choose Python.
 
 \subsection{Example 2}
-Since we have seen a fairly simple example above, lets take a look at a more complicated example.
+Now that we have looked at a fairly simple example above, lets take a look at a more complicated example.
 Do not be afraid if it does not make too much sense right now, but try and notice the similarities
 between the sudo language and the actual code examples.
 
@@ -259,11 +255,10 @@ else:
 \end{lstlisting}
 
 This example does a better job of showing how each language can tackle the concepts in a different manner but the core concepts
-laid out by the sudo language can still be extrapolated and translated to each individual programming language.
-As long as the language supports the concepts.
-As you may notice that I left out the implementation of C in this example.
-It is because C does not support the use of classes and objects, yes there are ways of completing this example in C using structs but that
+laid out by the sudo language can still be extrapolated and translated to each individual programming language; as long as the language supports the concepts.
+You may notice that I left out the implementation of C in this example.
+This is intentionally done because C does not support the use of classes and objects.  There are ways of completing this example in C using structs but that
 is something that you should learn on your own.
 \par
 
-So now you have seen a few examples, hopefully enough to give you an idea of how the examples in this resource will be presented.
+Hopefully the above examples will give you an understanding of how the rest of the examples in the book will be laid out.