diff --git a/book/src/config.md b/book/src/config.md
index 19600e1..c3d842c 100644
--- a/book/src/config.md
+++ b/book/src/config.md
@@ -23,7 +23,7 @@ The following global configuration options are supported:
 
 ### The `token` field
 
-The required `token` field is your Github Peronal Authentical Token as a
+The required `token` field is your Github Personal Authentical Token as a
 string.
 
 Example:
diff --git a/book/src/tutorial.md b/book/src/tutorial.md
index 3425752..17d16e9 100644
--- a/book/src/tutorial.md
+++ b/book/src/tutorial.md
@@ -119,7 +119,7 @@ Please remove this text!
 Here we've done two things:
 
 1. Create a "spanned inline" comment that attaches our comment to a block of
-   lines. If we ommitted the leading newline, we would have a regular "inline"
+   lines. If we omitted the leading newline, we would have a regular "inline"
    comment that attaches to the most immediately quoted line. Using spanned
    inline comments can be useful when we want to be precise during review.
 1. Snip the trailing text. We didn't have to do this, but it makes the example
diff --git a/src/parser.rs b/src/parser.rs
index a04c4a6..e8cb50d 100644
--- a/src/parser.rs
+++ b/src/parser.rs
@@ -213,7 +213,7 @@ fn parse_hunk_start(line: &str) -> Result<Option<(u64, u64)>> {
             .context("Failed to parse hunk start right line")?;
         // Note that for newly added files or deleted files, both sides
         // of the line info might be zero. `saturating_*` operations must hence
-        // be used for the following substraction to be safe.
+        // be used for the following subtraction to be safe.
 
         return Ok(Some((hunk_start_line_left, hunk_start_line_right)));
     }