diff --git a/src/doc/build-script.md b/src/doc/build-script.md
index f5ece41c382..b78e4d270d1 100644
--- a/src/doc/build-script.md
+++ b/src/doc/build-script.md
@@ -27,7 +27,7 @@ Some example use cases of the build command are:
 * Building a bundled C library.
 * Finding a C library on the host system.
 * Generating a Rust module from a specification.
-* Performing any platform-specific configuration neeeded for the crate.
+* Performing any platform-specific configuration needed for the crate.
 
 Each of these use cases will be detailed in full below to give examples of how
 the build command works.
@@ -202,7 +202,7 @@ authors = ["you@example.com"]
 build = "build.rs"
 ```
 
-Here we can se we've got a build script specified which we'll use to generate
+Here we can see we've got a build script specified which we'll use to generate
 some code. Let's see what's inside the build script:
 
 ```rust,no_run
@@ -224,10 +224,10 @@ fn main() {
 
 There's a couple of points of note here:
 
-* The script uses the `OUT_DIR` environment variable to discover where the ouput
-  files should be located. It can use the process's current working directory to
-  find where the input files should be located, but in this case we don't have
-  any input files.
+* The script uses the `OUT_DIR` environment variable to discover where the
+  output files should be located. It can use the process's current working
+  directory to find where the input files should be located, but in this case we
+  don't have any input files.
 * This script is relatively simple as it just writes out a small generated file.
   One could imagine that other more fanciful operations could take place such as
   generating a Rust module from a C header file or another language definition,
diff --git a/src/doc/guide.md b/src/doc/guide.md
index f6c5a31b360..41af8226a24 100644
--- a/src/doc/guide.md
+++ b/src/doc/guide.md
@@ -245,7 +245,7 @@ rev = "bf739419e2d31050615c1ba1a395b474269a4"
 
 Now, our builds will be the same. But, there's a big drawback: now we have to
 manually think about SHA-1s every time we want to update our library. This is
-both tedius and error prone.
+both tedious and error prone.
 
 Enter the `Cargo.lock`. Because of its existence, we don't need to manually
 keep track of the exact revisions: Cargo will do it for us. When we have a
diff --git a/src/doc/pkgid-spec.md b/src/doc/pkgid-spec.md
index c5e86b3715f..2dc686affcc 100644
--- a/src/doc/pkgid-spec.md
+++ b/src/doc/pkgid-spec.md
@@ -38,7 +38,7 @@ registry at `crates.io`
 
 ## Brevity of Specifications
 
-The goal of this is to enable both succinct and exhausitive syntaxes for
+The goal of this is to enable both succinct and exhaustive syntaxes for
 referring to packages in a dependency graph. Ambiguous references may refer to
 one or more packages. Most commands generate an error if more than one package
 could be referred to with the same specification.