Skip to content

Commit d8bccc8

Browse files
committed
Tutorial - fix minor spelling issues
1 parent d084c45 commit d8bccc8

File tree

5 files changed

+10
-10
lines changed

5 files changed

+10
-10
lines changed

etc/doc/tutorial/10.1-Set-and-Get.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ set :intensity, 3000
3030

3131
In the above example, as we stored both numbers under the same key, the
3232
last call to `set` 'wins', so the number associated with `:intensity`
33-
will be `3000` as the first call to `set` is effectively overriden.
33+
will be `3000` as the first call to `set` is effectively overridden.
3434

3535
## Get
3636

@@ -156,7 +156,7 @@ live_loop :sorted do
156156
end
157157
```
158158

159-
Notice how this code is pretty much idential to the version using
159+
Notice how this code is pretty much identical to the version using
160160
variable before it. However when you run the code, it behaves as you
161161
would expect with any typical Sonic Pi code - *it does the same thing
162162
every time* in this case thanks to the Time State system.

etc/doc/tutorial/11-MIDI.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ syntax and sound system can be exciting and put you into a new creative
88
position. However, sometimes it is essential to break out of the code
99
into the real world. We want two extra things:
1010

11-
1. To be able to convert actions in the real world into Sonic Pi events to work with programtically
11+
1. To be able to convert actions in the real world into Sonic Pi events to code with
1212
2. To be able to use Sonic Pi's strong timing model and semantics to control and manipulate objects in the real world
1313

1414
Luckily there's a protocol that's been around since the 80s that enables

etc/doc/tutorial/11.1-MIDI-In.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ room: http://gitter.im/samaaron/sonic-pi
2626
## Receiving MIDI Events
2727

2828
Once your device is connected, Sonic Pi will automatically receive
29-
events. You can see for yourself by manipulating yoru MIDI device and
29+
events. You can see for yourself by manipulating your MIDI device and
3030
looking at the cue logger in the bottom right of the application window
3131
below the log (if this isn't visible go to Preferences->Editor->Show &
3232
Hide and enable the 'Show cue log' tickbox). You'll see a stream of
@@ -136,7 +136,7 @@ that easy!
136136
## Getting Values
137137

138138
Finally, as our MIDI events are going straight into the Time State, we
139-
can also use the `get` fn to retreive the last seen value. This doesn't
139+
can also use the `get` fn to retrieve the last seen value. This doesn't
140140
block the current thread and returns `nil` if there's no value to be
141141
found (which you can override by passing a default value - see the docs
142142
for `get`). Remember that you can call `get` in any thread at any time

etc/doc/tutorial/11.2-MIDI-Out.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
# MIDI Out
44

55
In addition to receiving MIDI events we can also send out MIDI events to
6-
trigger and control external hardward synths, keyboards and other
6+
trigger and control external hardware synths, keyboards and other
77
devices. Sonic Pi provides a full set of fns for sending various MIDI messages such as:
88

99
1. Note on - `midi_note_on`

etc/doc/tutorial/12.1-Receiving-OSC.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ By default when Sonic Pi is launched it listens to port 4559 for
66
incoming OSC messages from programs on the same computer. This means
77
that without any configuration, you can send Sonic Pi an OSC message and
88
it will be displayed in the cue log just like incoming MIDI
9-
messages. This also means that any incomign OSC message is also
9+
messages. This also means that any incoming OSC message is also
1010
automatically added to the Time State which means you can also use `get`
1111
and `sync` to work with the incoming data - just like with MIDI.
1212

@@ -64,12 +64,12 @@ address (a unique identifier for your computer on your network - kind of
6464
like a phone number or an email address). You can discover the IP
6565
address of your computer by looking at the IO section of the preferences
6666
pane. (If your machine happens to have more than one IP address,
67-
hovering the mouse over the listed address will popup a list of all
68-
known addresses).
67+
hovering the mouse over the listed address will pop up with a list of
68+
all known addresses).
6969

7070
Note, some programs such as TouchOSC for iPhone and Android support
7171
sending OSC as a standard feature. So, once you're listening to remote
72-
machines and know your IP adress you can instantly start sending
72+
machines and know your IP address you can instantly start sending
7373
messages from apps like TouchOSC which enable you to build your own
7474
custom touch controls with sliders, buttons, dials etc. This can provide
7575
you with an enormous range of input options.

0 commit comments

Comments
 (0)