cloud-init-dev team mailing list archive

[Sean Bright <sean.bright@xxxxxxxxx>]

Sean Bright has proposed merging ~sbright/cloud-init:various-doc-fixes into cloud-init:master.

Requested reviews:
  cloud init development team (cloud-init-dev)

For more details, see:
https://code.launchpad.net/~sbright/cloud-init/+git/cloud-init/+merge/311313

Various minor fixes for the RTD documentation.
-- 
Your team cloud init development team is requested to review the proposed merge of ~sbright/cloud-init:various-doc-fixes into cloud-init:master.

diff --git a/doc/rtd/topics/boot.rst b/doc/rtd/topics/boot.rst
index 9d42336..859409a 100644
--- a/doc/rtd/topics/boot.rst
+++ b/doc/rtd/topics/boot.rst
@@ -21,7 +21,7 @@ boot goals.  By default, this generator will enable cloud-init.  It will
 not enable cloud-init if either:
 
  * A file exists: ``/etc/cloud/cloud-init.disabled``
- * The kernel command line as fond in /proc/cmdline contains ``cloud-init=disabled``.
+ * The kernel command line as found in /proc/cmdline contains ``cloud-init=disabled``.
    When running in a container, the kernel command line is not honored, but
    cloud-init will read an environment variable named ``KERNEL_CMDLINE`` in
    its place.
@@ -56,7 +56,7 @@ is rendered.  This includes clearing of all previous (stale) configuration
 including persistent device naming with old mac addresses.
 
 This stage must block network bring-up or any stale configuration might
-already have been applied.  That could have negative effects such as DCHP
+already have been applied.  That could have negative effects such as DHCP
 hooks or broadcast of an old hostname.  It would also put the system in
 an odd state to recover from as it may then have to restart network
 devices.
diff --git a/doc/rtd/topics/format.rst b/doc/rtd/topics/format.rst
index 5898d17..ed87d3e 100644
--- a/doc/rtd/topics/format.rst
+++ b/doc/rtd/topics/format.rst
@@ -9,7 +9,7 @@ Gzip Compressed Content
 
 Content found to be gzip compressed will be uncompressed.
 The uncompressed data will then be used as if it were not compressed. 
-This is typically is useful because user-data is limited to ~16384 [#]_ bytes.
+This is typically useful because user-data is limited to ~16384 [#]_ bytes.
 
 Mime Multi Part Archive
 =======================
diff --git a/doc/rtd/topics/logging.rst b/doc/rtd/topics/logging.rst
index c6afca1..4fd7e28 100644
--- a/doc/rtd/topics/logging.rst
+++ b/doc/rtd/topics/logging.rst
@@ -22,7 +22,7 @@ output to ``tee``, or ``logger``. If only a filename is provided, cloud-init
 will append its output to the file as though ``>>`` was specified.
 
 By default, cloud-init loads its output configuration from
-``/etc/cloud/coud.cfg.d/05_logging.cfg``. The default config directs both
+``/etc/cloud/cloud.cfg.d/05_logging.cfg``. The default config directs both
 stdout and stderr from all cloud-init stages to
 ``/var/log/cloud-init-output.log``. The default config is given as ::