-- 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
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
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
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:
----------------