knife-bootstrap.1 in chef-0.10.10.beta.1

- old
+ new

@@ -1,9 +1,9 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "KNIFE\-BOOTSTRAP" "1" "December 2011" "Chef 0.10.8" "Chef Manual"
+.TH "KNIFE\-BOOTSTRAP" "1" "April 2012" "Chef 0.10.10.beta.1" "Chef Manual"
 .
 .SH "NAME"
 \fBknife\-bootstrap\fR \- Install Chef Client on a remote host
 .
 .SH "SYNOPSIS"
@@ -56,12 +56,12 @@
 .TP
 \fB\-d\fR, \fB\-\-distro DISTRO\fR
 Bootstrap a distro using a template
 .
 .TP
-\fB\-\-no\-host\-key\-verify\fR
-Disable host key verification
+\fB\-\-[no\-]host\-key\-verify\fR
+Enable host key verification, which is the default behavior\.
 .
 .SH "DESCRIPTION"
 Performs a Chef Bootstrap on the target node\. The goal of the bootstrap is to get Chef installed on the target system so it can run Chef Client with a Chef Server\. The main assumption is a baseline OS installation exists\. This sub\-command is used internally by some cloud computing plugins\.
 .
 .P
@@ -94,10 +94,10 @@
 ubuntu10\.04\-apt
 .
 .IP "" 0
 .
 .P
-The gems installations will use RubyGems 1\.3\.6 and Chef installed as a gem\. The apt installation will use the Opscode APT repository\. The RubyGems installation requires installing gems with native extensions, so development related packages (ruby\-dev, build\-essential) are installed\. These are not installed with the apt installation, as native extensions are already compiled in the required packages\.
+The gems installations will use RubyGems 1\.3\.6 and Chef installed as a gem\. The apt installation will use the Opscode APT repository\.
 .
 .P
 In addition to handling the software installation, these bootstrap templates do the following:
 .
 .IP "\(bu" 4