diff --git a/README.markdown b/README.markdown
index 0cea45a2..2a353482 100644
--- a/README.markdown
+++ b/README.markdown
@@ -21,10 +21,10 @@ So what usually happens is either:
 
  * Large programs with configure scripts disabling line editing if readline is not present in the system, or not supporting it at all since readline is GPL licensed and libedit (the BSD clone) is not as known and available as readline is (real world example of this problem: Tclsh).
  * Smaller programs not using a configure script not supporting line editing at all (A problem we had with `redis-cli`, for instance).
- 
+
 The result is a pollution of binaries without line editing support.
 
-So I spent more or less two hours doing a reality check resulting in this little library: is it *really* needed for a line editing library to be 20k lines of code? Apparently not, it is possibe to get a very small, zero configuration, trivial to embed library, that solves the problem. Smaller programs will just include this, supporting line editing out of the box. Larger programs may use this little library or just checking with configure if readline/libedit is available and resorting to Linenoise if not.
+So I spent more or less two hours doing a reality check resulting in this little library: is it *really* needed for a line editing library to be 20k lines of code? Apparently not, it is possible to get a very small, zero configuration, trivial to embed library, that solves the problem. Smaller programs will just include this, supporting line editing out of the box. Larger programs may use this little library or just checking with configure if readline/libedit is available and resorting to Linenoise if not.
 
 ## Terminals, in 2010.
 
@@ -117,7 +117,7 @@ Linenoise supporst history, so that the user does not have to retype
 again and again the same things, but can use the down and up arrows in order
 to search and re-edit already inserted lines of text.
 
-The followings are the history API calls:
+The following are the history API calls:
 
     int linenoiseHistoryAdd(const char *line);
     int linenoiseHistorySetMaxLen(int len);
@@ -147,7 +147,7 @@ available for editing.
 
 Sometimes it is useful to allow the user to type passwords or other
 secrets that should not be displayed. For such situations linenoise supports
-a "mask mode" that will just replace the characters the user is typing 
+a "mask mode" that will just replace the characters the user is typing
 with `*` characters, like in the following example:
 
     $ ./linenoise_example
@@ -319,7 +319,7 @@ void stdinHasSomeData(void) {
 
 Now that we have a way to avoid blocking in the user input, we can use
 two calls to hide/show the edited line, so that it is possible to also
-show some input that we received (from socekts, bluetooth, whatever) on
+show some input that we received (from sockets, bluetooth, whatever) on
 screen:
 
     linenoiseHide(&ls);
diff --git a/example.c b/example.c
index 3676f92e..4bdfcd5e 100644
--- a/example.c
+++ b/example.c
@@ -122,7 +122,7 @@ int main(int argc, char **argv) {
         } else if (!strncmp(line, "/unmask", 7)) {
             linenoiseMaskModeDisable();
         } else if (line[0] == '/') {
-            printf("Unreconized command: %s\n", line);
+            printf("Unrecognized command: %s\n", line);
         }
         free(line);
     }