From 6d9e27b5b7123cda957621a7cc0ef6ae97c9a842 Mon Sep 17 00:00:00 2001
From: "Frederic Roussel\"" <fr.frasc@gmail.com>
Date: Tue, 17 Nov 2009 10:01:22 -0800
Subject: Fix typos and adjust some documentation.


diff --git a/Makefile.in b/Makefile.in
index 8fe4912..462b8bf 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -129,7 +129,7 @@ docs/ct-ng.1.gz: docs/ct-ng.1
 
 # We create a script fragment that is parseable from inside a Makefile,
 # but also from inside a shell script, hence the reason why we don't
-# use := to set varaibles, although that will incur a (very small)
+# use := to set variables, although that will incur a (very small)
 # penalty from the Makefile that includes it (due to re-evaluation at
 # each call).
 paths.mk:
diff --git a/docs/overview.txt b/docs/overview.txt
index 11cd5b2..94c1f86 100644
--- a/docs/overview.txt
+++ b/docs/overview.txt
@@ -366,22 +366,22 @@ Stopping and restarting a build |
 
 If you want to stop the build after a step you are debugging, you can pass the
 variable STOP to make:
-  ct-ng STOP=some_step
+  ct-ng build STOP=some_step
 
 Conversely, if you want to restart a build at a specific step you are
 debugging, you can pass the RESTART variable to make:
-  ct-ng RESTART=some_step
+  ct-ng build RESTART=some_step
 
 Alternatively, you can call make with the name of a step to just do that step:
   ct-ng libc_headers
 is equivalent to:
-  ct-ng RESTART=libc_headers STOP=libc_headers
+  ct-ng build RESTART=libc_headers STOP=libc_headers
 
 The shortcuts +step_name and step_name+ allow to respectively stop or restart
 at that step. Thus:
-  ct-ng +libc_headers        and:    ct-ng libc_headers+
+  ct-ng +libc_headers              and:    ct-ng libc_headers+
 are equivalent to:
-  ct-ng STOP=libc_headers    and:    ct-ng RESTART=libc_headers
+  ct-ng build STOP=libc_headers    and:    ct-ng build RESTART=libc_headers
 
 To obtain the list of acceptable steps, please call:
   ct-ng list-steps
-- 
cgit v0.10.2-6-g49f6