From 88ee587cf054e0cd9424ef10d22629ac2b5c0eaf Mon Sep 17 00:00:00 2001
From: Ralph Giles <giles@thaumas.net>
Date: Sun, 6 Feb 2011 21:42:58 -0800
Subject: Fix various typos.

---
 manual.asciidoc | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/manual.asciidoc b/manual.asciidoc
index 84e475d..3038d46 100644
--- a/manual.asciidoc
+++ b/manual.asciidoc
@@ -48,7 +48,7 @@ A build file (default name: `build.ninja`) provides a list of _rules_
 -- short names for longer commands, like how to run the compiler --
 along with a list of _build_ statements saying how to build files
 using the rules -- which rule to apply to which inputs to produce
-which ouputs.
+which outputs.
 
 Conceptually, `build` statements describe the dependency graph of your
 project, while `rule` statements describe how to generate the files
@@ -89,7 +89,7 @@ Some explicit _non-goals_:
   paths. _Making decisions is slow._
 
 To restate, Ninja is faster than other build systems because it is
-painfully simple.  You must tell Ninja exctly what to do when you
+painfully simple.  You must tell Ninja exactly what to do when you
 create your project's `.ninja` files.
 
 Comparison to GNU make
@@ -154,7 +154,7 @@ are the resulting binary and this manual.
 Creating .ninja files
 ---------------------
 Here's a basic `.ninja` file that demonstrates most of the syntax.
-It wil be used as an example for for the following sections.
+It will be used as an example for the following sections.
 
 ---------------------------------
 cflags = -Wall
@@ -175,7 +175,7 @@ reusable names for strings.  A declaration like the following
 cflags = -g
 ----------------
 
-can be used on the right side of an equals sign, deferencing it with
+can be used on the right side of an equals sign, dereferencing it with
 a dollar sign, like this:
 
 ----------------
-- 
cgit v0.12

