Check spelling (#121)

blk/019

@@ -9,7 +9,7 @@ Many blocks contain code. That code can be interpreted through
 LOAD. Programs stored in blocks frequently have "loader blocks"
 that take care of loading all blocks relevant to the program.
 
-Blocks spanning multipls disks are tricky. If your media isn't
+Blocks spanning multiple disks are tricky. If your media isn't
 large enough to hold all Collapse OS blocks in one unit, you'll
 have to make it span multiple disks. Block reference in
 informational texts aren't a problem: When you swap your disk,

blk/086

@@ -1,6 +1,6 @@
 (cont.)
 0x2b: doesWord. This word is created by "DOES>" and is followed
-by a 2-byte value as well as the adress where "DOES>" was
+by a 2-byte value as well as the address where "DOES>" was
 compiled. At that address is an atom list exactly like in a
 compiled word. Upon execution, after having pushed its cell
 addr to PSP, it execute its reference exactly like a

blk/122

@@ -3,7 +3,7 @@ effect described below.
 
 Pressing a 0-9 digit accumulates that digit into what is named
 the "modifier". That modifier affects the behavior of many
-keystokes described below. The modifier starts at zero, but
+keystrokes described below. The modifier starts at zero, but
 most commands interpret a zero as a 1 so that they can have an
 effect.
 

blk/206

@@ -1,5 +1,5 @@
 On top of that, you have the very nice BREAK, instruction,
-which must also be preceeded by a JRxx, and will jump to the
+which must also be preceded by a JRxx, and will jump to the
 PC following the next AGAIN,
 
 

blk/264

@@ -10,7 +10,7 @@ compile it with offsets. We abort on IMMED? because we're
 never supposed to encounter an immediate at this point.
 
 If not found, we try the same word on system dict (RAM+02).
-If found and is immediate, execute. If founf and not immediate,
+If found and is immediate, execute. If found and not immediate,
 error. If not found, try number.
 
 

blk/388

@@ -2,7 +2,7 @@
     ( buffer overflow? same as if we typed a newline )
     IN> @ IN) = IF 0x0a ELSE KEY THEN ( c )
     DUP 0x0a = IF DROP 0xd THEN ( lf? same as cr )
-    ( bacspace? handle and exit )
+    ( backspace? handle and exit )
     DUP BS? IF _bs EXIT THEN
     ( echo back )
     DUP EMIT ( c )

blk/422

@@ -13,4 +13,4 @@ Core words (low) (B350)
 Then comes the part where we begin defining words in Forth.
 Core words are designed to be cross-compiled (B260), from a
 full Forth interpreter. This means that it has access to more
-than boot words. This somes with tricky limitations.    (cont.)
+than boot words. This comes with tricky limitations.    (cont.)

blk/552

@@ -6,7 +6,7 @@ to scroll more efficiently. Instead of having to copy the LCD
 ram around at each linefeed (or instead of having to maintain
 an in-memory buffer), we can use this feature.
 
-The Z-Offet goes upwards, with wrapping. For example, if we
+The Z-Offset goes upwards, with wrapping. For example, if we
 have an 8 pixels high line at row 0 and if our offset is 8,
 that line will go up 8 pixels, wrapping itself to the bottom of
 the screen.

blk/632

@@ -7,7 +7,7 @@ Start - A - C - B - Right - Left - Down - Up
 Each bit is high when button is unpressed and low if button is
 pressed. When no button is pressed, 0xff is returned.
 This logic below is for the Genesis controller, which is modal.
-TH is an output pin that swiches the meaning of TL and TR. When
+TH is an output pin that switches the meaning of TL and TR. When
 TH is high (unselected), TL = Button B and TR = Button C. When
 TH is low (selected), TL = Button A and TR = Start. )