Fix typos in lb_config.1.

1 files changed, 29 insertions, 28 deletions

diff --git a/manpages/pot/lb_config.1.pot b/manpages/pot/lb_config.1.pot
index 78234ca18..22d4b1cd0 100644
--- a/manpages/pot/lb_config.1.pot
+++ b/manpages/pot/lb_config.1.pot
@@ -7,7 +7,7 @@
 msgid ""
 msgstr ""
 "Project-Id-Version: live-build 4.0.1-1\n"
-"POT-Creation-Date: 2014-08-28 23:25+0200\n"
+"POT-Creation-Date: 2014-09-07 13:13+0900\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -889,7 +889,7 @@ msgstr ""
 #: en/lb_config.1:258
 msgid ""
 "defines if deb-src entries should be included in the resulting live image or "
-"not, defaults to on."
+"not, defaults to true."
 msgstr ""
 
 #. type: IP
@@ -905,7 +905,7 @@ msgid ""
 "to the host architecture. Note that you cannot crossbuild for another "
 "architecture if your host system is not able to execute binaries for the "
 "target architecture natively. For example, building amd64 images on i386 and "
-"vice versa is possile if you have a 64bit capable i386 processor and the "
+"vice versa is possible if you have a 64bit capable i386 processor and the "
 "right kernel. But building powerpc images on an i386 system is not possible."
 msgstr ""
 
@@ -976,8 +976,8 @@ msgstr ""
 #. type: Plain text
 #: en/lb_config.1:270
 msgid ""
-"defines which bootloader is beeing used in the generated image. This has "
-"only an effect if the selected binary image type does allow to choose the "
+"defines which bootloader is being used in the generated image. This has only "
+"an effect if the selected binary image type does allow to choose the "
 "bootloader. For example, if you build a iso, always syslinux (or more "
 "precise, isolinux) is being used. Also note that some combinations of binary "
 "images types and bootloaders may be possible but live-build does not support "
@@ -1009,7 +1009,7 @@ msgstr ""
 #: en/lb_config.1:274
 msgid ""
 "defines globally if any cache should be used at all. Different caches can be "
-"controled through the their own options."
+"controlled through the their own options."
 msgstr ""
 
 #. type: IP
@@ -1036,7 +1036,7 @@ msgstr ""
 #: en/lb_config.1:278
 msgid ""
 "defines if downloaded packages files should be cached which is true by "
-"default. Disabling it does save space consumtion in your build directory, "
+"default. Disabling it does save space consumption in your build directory, "
 "but remember that you will cause much unnecessary traffic if you do a couple "
 "of rebuilds. In general you should always leave it true, however, in some "
 "particular rare build setups, it can be faster to refetch packages from the "
@@ -1070,7 +1070,7 @@ msgstr ""
 msgid ""
 "defines if the binary image should contain a file called md5sums.txt, "
 "sha1sums.txt and/or sha256sums.txt. These lists all files on the image "
-"together with their checksums. This in turn can be used by live-boots built-"
+"together with their checksums. This in turn can be used by live-boot's built-"
 "in integrity-check to verify the medium if specified at boot prompt. In "
 "general, this should not be false and is an important feature of live system "
 "released to the public. However, during development of very big images it "
@@ -1112,15 +1112,16 @@ msgstr ""
 #. type: Plain text
 #: en/lb_config.1:288
 msgid ""
-"defines whetever live-build should use the tools from within the chroot to "
-"build the binary image or not by using and including the host systems tools. "
-"This is a very dangerous option, using the tools of the host system can lead "
-"to tainted and even non-bootable images if the host systems version of the "
-"required tools (mainly these are the bootloaders such as syslinux and grub, "
-"and the auxilliary tools such as dosfstools, xorriso, squashfs-tools and "
-"others) do not B<exactely> match what is present at build-time in the target "
-"distribution. Never do disable this option unless you are B<exactely> sure "
-"what you are doing and have B<completely>I< understood its consequences.>"
+"defines whether live-build should use the tools from within the chroot to "
+"build the binary image or not by using and including the host system's "
+"tools. This is a very dangerous option, using the tools of the host system "
+"can lead to tainted and even non-bootable images if the host systems version "
+"of the required tools (mainly these are the bootloaders such as syslinux and "
+"grub, and the auxiliary tools such as dosfstools, xorriso, squashfs-tools "
+"and others) do not B<exactly> match what is present at build-time in the "
+"target distribution. Never do disable this option unless you are B<exactly> "
+"sure what you are doing and have B<completely>I< understood its consequences."
+">"
 msgstr ""
 
 #. type: IP
@@ -1135,9 +1136,9 @@ msgid ""
 "defines which filesystem type should be used for the root filesystem image. "
 "If you use none, then no filesystem image is created and the root filesystem "
 "content is copied on the binary image filesystem as flat files. Depending on "
-"what binary filesystem you have choosen, it may not be possible to build "
-"with such a plain root filesystem, e.g. fat16/fat32 will not work as linux "
-"does not support to run directly on them."
+"what binary filesystem you have chosen, it may not be possible to build with "
+"such a plain root filesystem, e.g. fat16/fat32 will not work as linux does "
+"not support to run directly on them."
 msgstr ""
 
 #. type: IP
@@ -1176,7 +1177,7 @@ msgstr ""
 #: en/lb_config.1:296
 msgid ""
 "defines what value the debconf frontend should be set to inside the chroot. "
-"Note that setting it to anything by noninteractive, which is the default, "
+"Note that setting it to anything but noninteractive, which is the default, "
 "makes your build asking questions during the build."
 msgstr ""
 
@@ -1189,7 +1190,7 @@ msgstr ""
 #. type: Plain text
 #: en/lb_config.1:298
 msgid ""
-"defines what value the debconf priority shoul dbe set to inside the chroot. "
+"defines what value the debconf priority should be set to inside the chroot. "
 "By default, it is set to critical, which means that almost no questions are "
 "displayed. Note that this only has an effect if you use any debconf frontend "
 "different from noninteractive."
@@ -1207,10 +1208,10 @@ msgid ""
 "defines which type, if any, of the debian-installer should be included in "
 "the resulting binary image. By default, no installer is included. All "
 "available flavours except live are the identical configurations used on the "
-"installer media produced by regular debian-cd. When live is choosen, the "
-"live-installer udeb is included so that debian-installer will behave "
-"different than usual - instead of installing the debian system from packages "
-"from the medium or the network, it installs the live system to the disk."
+"installer media produced by regular debian-cd. When live is chosen, the live-"
+"installer udeb is included so that debian-installer will behave different "
+"than usual - instead of installing the debian system from packages from the "
+"medium or the network, it installs the live system to the disk."
 msgstr ""
 
 #. type: IP
@@ -1488,7 +1489,7 @@ msgstr ""
 msgid ""
 "sets the PREPARER field in the header of a resulting CD/DVD image. By "
 "default this is set to \"live-build I<VERSION>; http://packages.qa.debian."
-"org/live-build\", whereas VERSION is expanded to the version of live-build "
+"org/live-build\", where VERSION is expanded to the version of live-build "
 "that was used to build the image."
 msgstr ""
 
@@ -1531,7 +1532,7 @@ msgstr ""
 #. type: Plain text
 #: en/lb_config.1:346
 msgid ""
-"sets the eraseblock size for a JFFS2 (Second Journalling Flash File System) "
+"sets the eraseblock size for a JFFS2 (Second Journaling Flash File System) "
 "filesystem. The default is 64 KiB. If you use an erase block size different "
 "than the erase block size of the target MTD device, JFFS2 may not perform "
 "optimally. If the SIZE specified is below 4096, the units are assumed to be "