From 3382976433fa09b4b069c25242ec29e302a4c691 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Johan=20Sundstr=C3=B6m?= Date: Mon, 12 Aug 2013 18:47:06 -0700 Subject: [PATCH] Proof reading --- doc/manual.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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. -- 2.7.4