doc typos

sonic-pi-net · Nov 21, 2014 · 8388ce1 · 8388ce1
1 parent adfc4e9
commit 8388ce1
Show file tree

Hide file tree

Showing 5 changed files with 17 additions and 11 deletions.
diff --git a/etc/doc/tutorial/02.1-Synth-Params.md b/etc/doc/tutorial/02.1-Synth-Params.md
@@ -10,7 +10,7 @@ First, let's look at what parameters actually are.
 
 ## Parameters
 
-Sonic Pi supports the notion of parameters for its synths Parameters are
+Sonic Pi supports the notion of parameters for its synths. Parameters are
 controls you pass to `play` which modify and control aspects
 of the sound you hear. Each synth has its own set of parameters for
 finely tuning its sound. However, there are common sets of parameters
@@ -45,7 +45,7 @@ play 50, beans: 0.5, cheese: 1
 ```
 
 Parameters that aren't recognised by the synth are just ignored (like
-`cheese` and `beans` which are clearly ridiculous param names!).
+`cheese` and `beans` which are clearly ridiculous param names!)
 
 If you accidentally use the same parameter twice with different values,
 the last one wins. For example, `beans:` will have the value 2 rather

diff --git a/etc/doc/tutorial/03.2-Sample-Params.md b/etc/doc/tutorial/03.2-Sample-Params.md
@@ -2,7 +2,7 @@
 
 As we saw with synths we can easily control our sounds with
 parameters. Samples support exactly the same parameterisation
-mechanism. Let's revisit at our friends `amp:` and `pan:`.
+mechanism. Let's revisit our friends `amp:` and `pan:`.
 
 ## Amping samples
 

diff --git a/etc/doc/tutorial/04.2-Iteration-and-Loops.md b/etc/doc/tutorial/04.2-Iteration-and-Loops.md
@@ -12,7 +12,7 @@ powerful new tools. First up is iteration and loops.
 
 ## Repetition
 
-Have you written some code you'd like to repeat a few times. For
+Have you written some code you'd like to repeat a few times? For
 example, you might have something like this:
 
 ```
@@ -57,7 +57,13 @@ wanted to make a change.
 
 ## Iteration
 
-What repeating the code as as easy as saying *do this three times*. Well, it pretty much is. Remember our old friend the code block that we met in the previous section on FX? We can use it to mark the start and of the code we'd like to repeat three times. We then use the special code `3.times`. So, instead of writing do this three times, we write `3.times do` - that's not too hard. Just remember to write `end` and the end of the code you'd like to repeat:
+In fact, repeating the code is as easy as saying *do this three
+times*. Well, it pretty much is. Remember our old friend the code
+block? We can use it to mark the start and end of the code we'd like
+to repeat three times. We then use the special code `3.times`. So,
+instead of writing *do this three times*, we write `3.times do` -
+that's not too hard. Just remember to write `end` at the end of the
+code you'd like to repeat:
 
 ```
 3.times do
@@ -92,8 +98,8 @@ end
 
 ## Nesting Iterations
 
-Just like nesting FX, we can put iterations inside other iterations to
-create interesting patterns. For example:
+We can put iterations inside other iterations to create interesting
+patterns. For example:
 
 ```
 4.times do

diff --git a/etc/doc/tutorial/04.5-Functions.md b/etc/doc/tutorial/04.5-Functions.md
@@ -18,7 +18,7 @@ end
 
 Here, we've defined a new function called `foo`. We do this with our old
 friend the do/end block and the magic code `define` followed by the name
-we wish to give our function. We didn't have to call it `foo` we could
+we wish to give our function. We didn't have to call it `foo`, we could
 have called it anything we want such as `bar`, `baz` or ideally
 something meaningful to you like `main_section` or `lead_riff`.
 
@@ -74,7 +74,7 @@ starting with the letters `def...` such as `defonce`.
 
 For those of you that would like to see a more advanced feature of
 functions you might be interested in knowing that just like you can pass
-min and max values to `rrand` you can teach your functions to accept
+min and max values to `rrand`, you can teach your functions to accept
 arguments. Let's take a look:
 
 ```
@@ -91,7 +91,7 @@ This isn't very exciting but it illustrates the point. We've created our
 own version of `play` called `my_player` which is parameterised.
 
 The parameters need to go after the `do` of the `define` do/end block,
-surrounded by vertical goalposts `|`. and separated by commas `,`. You
+surrounded by vertical goalposts `|` and separated by commas `,`. You
 may use any words you want for the parameter names.
 
 The magic happens inside the `define` do/end block. You may use the

diff --git a/etc/doc/tutorial/04.6-Variables.md b/etc/doc/tutorial/04.6-Variables.md
@@ -53,7 +53,7 @@ sleep sample_duration(:loop_amen)
 ```
 
 Which, of course, is a very nice way of communicating the intent of the
-code. One reason is to manage repetition.
+code.
 
 ## Managing Repetition
-Original file line number
+Diff line change
@@ Expand Up / @@ -53,7 +53,7 @@ sleep sample_duration(:loop_amen) @@
     ```
     Which, of course, is a very nice way of communicating the intent of the
-    code. One reason is to manage repetition.
+    code.
     ## Managing Repetition
@@ Expand Down @@