spell check

4 files changed, 7 insertions, 7 deletions

diff --git a/public/bash-arrays.md b/public/bash-arrays.md
index 480d168..e78b8d5 100644
--- a/public/bash-arrays.md
+++ b/public/bash-arrays.md
@@ -7,7 +7,7 @@ that if you need arrays, you shouldn't be using Bash.  If we reject
 the notion that one should never use Bash for scripting, then thinking
 you don't need Bash arrays is what I like to call "wrong".
 
-The simple expanation of why everybody who programs in Bash needs to
+The simple explanation of why everybody who programs in Bash needs to
 understand arrays is this: command line arguments are exposed as an
 array.  Does your script take any arguments on the command line?
 Great, you need to work with an array!
@@ -53,7 +53,7 @@ difference between `@` and `*`.
     </tr><tr>
       <td><code>"${array[*]}"</code></td>
       <td>Returns every element of the array in a single
-          whitepace-separated string.</td>
+          whitespace-separated string.</td>
     </tr>
   </tbody>
 </table>
@@ -153,7 +153,7 @@ with letters and underscore), that *mostly* match up with the normal
 array syntax.
 
 Setting the arguments array, on the other hand, is pretty different.
-That's fine, because setting the arguments array is less usefull
+That's fine, because setting the arguments array is less useful
 anyway.
 
 <table>
diff --git a/public/emacs-as-an-os.md b/public/emacs-as-an-os.md
index 5fe6d4f..c22cd15 100644
--- a/public/emacs-as-an-os.md
+++ b/public/emacs-as-an-os.md
@@ -22,7 +22,7 @@ uncommon, historically; the filesystem is a little stranger.
 
 The Lisp part of Emacs is the operating system that runs on that
 emulated hardware. It's not a particularly powerful OS, it not a
-multi-tasking system. It has many packages available for it (though
+multitasking system. It has many packages available for it (though
 not until recently was there a official package manager). It has
 reasonably powerful IPC mechanisms. It has shells, mail clients (MUAs
 and MSAs), web browsers, web servers and more, all written entirely in
diff --git a/public/fs-licensing-explanation.md b/public/fs-licensing-explanation.md
index df4f24d..3e30975 100644
--- a/public/fs-licensing-explanation.md
+++ b/public/fs-licensing-explanation.md
@@ -14,7 +14,7 @@ This is based on a post on [reddit][1], published on 2013-02-21.
 > individual. 
 >
 > [LiveCode is GPLv3, but also sells non-free licenses] Can you really
-> have the same code under two conflicting licences? Once licensed
+> have the same code under two conflicting licenses? Once licensed
 > under GPL3 wouldn't they too be required to adhere to its rules?
 
 I believe that GNU/the FSF has an FAQ that addresses this, but I can't
diff --git a/public/git-go-pre-commit.md b/public/git-go-pre-commit.md
index 74dca28..84137cc 100644
--- a/public/git-go-pre-commit.md
+++ b/public/git-go-pre-commit.md
@@ -7,7 +7,7 @@ One of the (many) wonderful things about the Go programming language
 is the `gofmt` tool, which formats your source in a canonical way.  I
 thought it would be nice to integrate this in my `git` workflow by
 adding it in a pre-commit hook to automatically format my source code
-when I commited it.
+when I committed it.
 
 The Go distribution contains a git pre-commit hook that checks whether
 the source code is formatted, and aborts the commit if it isn't.  I
@@ -15,7 +15,7 @@ don't remember if I was aware of this at the time (or if it even
 existed at the time, or if it is new), but I wanted it to go ahead and
 format the code for me.
 
-I found a few solutions online, but they wre all missing
+I found a few solutions online, but they were all missing
 something—support for partial commits.  I frequently use `git add
 -p`/`git gui` to commit a subset of the changes I've made to a file,
 the existing solutions would end up adding the entire set of changes