[PATCH 2/2] Fix typos and inaccuracies in docs and examples.
From: Yann Dirson <ydirson@free.fr>
---
examples/device_table.txt | 2 +-
pod/multistrap | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
Those are leftover from my http://bugs.debian.org/630314 patch. Given
their nature, I suppose you overlooked them ?
diff --git a/examples/device_table.txt b/examples/device_table.txt
index e44b984..75e24f1 100644
--- a/examples/device_table.txt
+++ b/examples/device_table.txt
@@ -29,7 +29,7 @@
# become root and then run 'mknod' a thousand times. Using a device
# table you can create device nodes and directories "on the fly".
# Furthermore, you can use a single table entry to create a many device
-# minors. For example, if I wanted to create /dev/hda and /dev/hda[0-15]
+# minors. For example, if I wanted to create /dev/hda and /dev/hda[1-15]
# I could just use the following two table entries:
# /dev/hda b 640 0 0 3 0 0 0 -
# /dev/hda b 640 0 0 3 1 1 1 15
diff --git a/pod/multistrap b/pod/multistrap
index 5560f6d..5d31dcf 100644
--- a/pod/multistrap
+++ b/pod/multistrap
@@ -431,7 +431,7 @@ directory of the rootfs.
One advantage of using machine:variant support is that the entire
rootfilesystem can be managed by a single call to multistrap - this
-is useful when building root filesystems in userspace.
+is useful when building root filesystems as non-priviledged user.
To enable machine:variant support, specify the path to the scripts to
be called in the variant configuration file (General section):
@@ -471,7 +471,7 @@ section.
addimportant=true
Priority: important can only operate for all sections listed in the
-C<boostrap> option. This may cause some confusion when mixing suites.
+C<bootstrap> option. This may cause some confusion when mixing suites.
It is not possible to enable addimportant and omitrequired in the
same configuration. C<multistrap> will exit with error code 7 if
--
1.7.5.4
Reply to: