From 4ecda82afa3ad2c9b51eb922a6e781ef6efe4b34 Mon Sep 17 00:00:00 2001
From: Fletcher Nichol <fnichol@nichol.ca>
Date: Tue, 3 Jul 2012 16:43:31 -0600
Subject: [PATCH] Clarify that knife server bootstrap is not a subcommand in
 README.

Closes #2
---
 CHANGELOG.md | 6 ++++++
 README.md    | 5 ++++-
 2 files changed, 10 insertions(+), 1 deletion(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index e179108..be379bd 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,11 @@
 ## 0.1.1.dev (unreleased)
 
+### Bug fixes
+
+* Issue [#2](https://github.com/fnichol/knife-server/issues/2): Improve
+  documentation to clarify `knife server bootstrap` is not a proper
+  subcommand. ([@fnichol][])
+
 
 ## 0.1.0 (June 23, 2012)
 
diff --git a/README.md b/README.md
index 0279f9d..ad9f437 100644
--- a/README.md
+++ b/README.md
@@ -76,7 +76,7 @@ from the [chef-bootstrap-repo][chef_bootstrap_repo] project?
 
 ## <a name="subcommands"></a> Subcommands
 
-### <a name="knife-server-bootstrap"></a> knife server bootstrap
+### <a name="knife-server-bootstrap"></a> knife server bootstrap (Common Options)
 
 These subcommands will install and configure an Open Source Chef Server on
 several different clouds/environments. The high level step taken are as
@@ -100,6 +100,9 @@ follows:
    already exists at that path a backup copy will be made in the same
    directory.
 
+**Note** `knife server bootstrap` can not be invoked directly; a subcommand
+must be selected which determines the provisioning strategy.
+
 #### Common Configuration
 
 ##### --node-name NAME (-N)