diff --git a/README.md b/README.md
index e7713a8..c286a93 100644
--- a/README.md
+++ b/README.md
@@ -4,11 +4,11 @@ This repository is a collection of `git subtree`s for published LFE books.
 
 Please do not issue pull requests against this repo, as it is essentially read-only.
 
-Acutal book content is mainted in Markdown files in `builder` branches (see the repositories linked below). Content is generated in `master` branches. Pull requests need to be issued against the Markdown files in the `builder` branches below.
+Actual book content is maintained in Markdown files in `builder` branches (see the repositories linked below). Content is generated in `master` branches. Pull requests need to be issued against the Markdown files in the `builder` branches below.
 
 Any feedback, bugs, requests, etc., should be filed against the appropriate book in the links below.
 
-Developers and contributers should scroll to the bottom of this file to read instructions on how to incorporate and publish changes to the LFE books.
+Developers and contributors should scroll to the bottom of this file to read instructions on how to incorporate and publish changes to the LFE books.
 
 ---
 
@@ -49,7 +49,7 @@ Developers and contributers should scroll to the bottom of this file to read ins
 # Developer / Contributor Notes
 
 1. To update a book, visit the repository for that book (linked above).
-1. For the repository, and clone to your machine.
+1. Clone the repository to your machine.
 1. Create a branch for your change, commit, and push to your fork.
 1. Issue a PR against the book publisher's repository for the book.
 
@@ -57,7 +57,7 @@ At this point, a reviewer will examine the change, provide feedback, and iterate
 
 Once approved, the changes will be merged to the `builder` branch and the reviewer will publish these changes to `master`.
 
-Then the reviewer will update the `master` branch that collects all publised LFE books ([https://github.com/lfe/books](https://github.com/lfe/books)) and push that up to Github, at which point you changes will show up for the given book.
+Then the reviewer will update the `master` branch that collects all published LFE books ([https://github.com/lfe/books](https://github.com/lfe/books)) and push that up to GitHub, at which point your changes will show up for the given book.
 
 # Reviewer Notes
 
@@ -65,4 +65,4 @@ When adding a new book to the repo, be sure to run `make` first: this will remin
 
 Once those changes are made, to add the actual content for a new book, run `make init-YOUR-BOOK`.
 
-To publish any changes made upstream (e.g., after the merging of a pull request), be sure to run `make publish` in your working directoy of this project. After that, the latest version of all books will be published.
+To publish any changes made upstream (e.g., after the merging of a pull request), be sure to run `make publish` in your working directory of this project. After that, the latest version of all books will be published.