diff options
| author | Johan Sundström <oyasumi@gmail.com> | 2013-08-13 01:47:06 (GMT) |
|---|---|---|
| committer | Johan Sundström <oyasumi@gmail.com> | 2013-08-13 01:47:06 (GMT) |
| commit | 3382976433fa09b4b069c25242ec29e302a4c691 (patch) | |
| tree | e4410840b67ac2b12c9da428ba650f0e41d4a224 /doc | |
| parent | 41bb28a553378cccb07285d103ffcde4e03e8797 (diff) | |
| download | Ninja-3382976433fa09b4b069c25242ec29e302a4c691.zip Ninja-3382976433fa09b4b069c25242ec29e302a4c691.tar.gz Ninja-3382976433fa09b4b069c25242ec29e302a4c691.tar.bz2 | |
Proof reading
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/manual.asciidoc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/manual.asciidoc b/doc/manual.asciidoc index 2900f28..a735257 100644 --- a/doc/manual.asciidoc +++ b/doc/manual.asciidoc @@ -54,7 +54,7 @@ Here are the design goals of Ninja: higher-level build systems have different opinions about how code should be built; for example, should built objects live alongside the sources or should all build output go into a separate directory? - Is there an "package" rule that builds a distributable package of + Is there a "package" rule that builds a distributable package of the project? Sidestep these decisions by trying to allow either to be implemented, rather than choosing, even if that results in more verbosity. |