[elpa] externals/sotlisp c2936c5 01/11: Fix some typos.

[Stefan Monnier]

branch: externals/sotlisp
commit c2936c5c17686dc4fd302bcdf55fe360eb983138
Author: John Kitchin <jkitchin@andrew.cmu.edu>
Commit: John Kitchin <jkitchin@andrew.cmu.edu>

    Fix some typos.
---
 README.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index a08172b..a8e2189 100644
--- a/README.md
+++ b/README.md
@@ -21,15 +21,15 @@ However, these are defined in a way such that they ONLY 
expand in a
 place where you would use a function, so hitting SPC after `(r`
 expands to `(require '`, but hitting SPC after `(delete-region r` will
 NOT expand the `r`, because that's obviously not a function.
-Furtheromre, `#'r` will expand to `#'require` (note how it ommits that
+Furtheromre, `#'r` will expand to `#'require` (note how it omits that
 extra quote, since it would be useless here).
 
 ## Commands
 
-It also defines 4 commands, which really fit into this "follow the
+It also defines four commands, which really fit into this "follow the
 thought-flow" way of writing.  The bindings are as follows, I
 understand these don't fully adhere to conventions, and I'd
-appreaciate suggestions on better bindings.
+appreciate suggestions on better bindings.
 
 - `M-RET` :: Break line, and insert "()" with point in the middle.
 - `C-RET` :: Do `forward-up-list', then do M-RET.
@@ -43,7 +43,7 @@ definition for it below the current function and leave point 
inside.
 - `C-c v` :: Same, but for variable.
 
 With these commands, you just write your code as you think of it.  Once
-you hit a "stop-point" of sorts in your tought flow, you hit `C-c f/v`
+you hit a "stop-point" of sorts in your thought flow, you hit `C-c f/v`
 on any undefined functions/variables, write their definitions, and hit
 `C-u C-SPC` to go back to the main function.