boot/*/Config.in: re-wrap help text

... to follow the convention <tab><2 spaces><62 chars>.

Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

boot/at91bootstrap/Config.in

@@ -4,9 +4,11 @@ config BR2_TARGET_AT91BOOTSTRAP
 	help
 	  AT91Bootstrap is a first level bootloader for the Atmel AT91
 	  devices. It integrates algorithms for:
-	  - Device initialization such as clock configuration, PIO settings...
+	  - Device initialization such as clock configuration, PIO
+	    settings...
 	  - Peripheral drivers such as PIO, PMC or SDRAMC...
-	  - Physical media algorithm such as DataFlash, NandFlash, NOR Flash...
+	  - Physical media algorithm such as DataFlash, NandFlash, NOR
+	    Flash...
 
 if	BR2_TARGET_AT91BOOTSTRAP
 

boot/at91bootstrap3/Config.in

@@ -4,9 +4,11 @@ config BR2_TARGET_AT91BOOTSTRAP3
 	help
 	  AT91Bootstrap is a first level bootloader for the Atmel AT91
 	  devices. It integrates algorithms for:
-	  - Device initialization such as clock configuration, PIO settings...
+	  - Device initialization such as clock configuration, PIO
+	    settings...
 	  - Peripheral drivers such as PIO, PMC or SDRAMC...
-	  - Physical media algorithm such as DataFlash, NandFlash, NOR Flash...
+	  - Physical media algorithm such as DataFlash, NandFlash, NOR
+	    Flash...
 
 if BR2_TARGET_AT91BOOTSTRAP3
 
@@ -20,8 +22,8 @@ config BR2_TARGET_AT91BOOTSTRAP3_LATEST_VERSION
 config BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_GIT
 	bool "Custom Git repository"
 	help
-	  This option allows Buildroot to get the AT91 Bootstrap 3 source
+	  This option allows Buildroot to get the AT91 Bootstrap 3
-	  code from a Git repository.
+	  source code from a Git repository.
 
 endchoice
 

boot/uboot/Config.in

@@ -11,14 +11,14 @@ choice
 config BR2_TARGET_UBOOT_BUILD_SYSTEM_LEGACY
 	bool "Legacy"
 	help
-	  Select this option if you use an old U-Boot (older than 2015.04),
+	  Select this option if you use an old U-Boot (older than
-	  so that we use the old build system.
+	  2015.04), so that we use the old build system.
 
 config BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG
 	bool "Kconfig"
 	help
-	  Select this option if you use a recent U-Boot version (2015.04 or
+	  Select this option if you use a recent U-Boot version (2015.04
-	  newer), so that we use the Kconfig build system.
+	  or newer), so that we use the Kconfig build system.
 
 endchoice
 
@@ -27,9 +27,9 @@ config BR2_TARGET_UBOOT_BOARDNAME
 	string "U-Boot board name"
 	help
 	  One of U-Boot supported boards to be built.
-	  This will be suffixed with _config to meet U-Boot standard naming.
+	  This will be suffixed with _config to meet U-Boot standard
-	  See boards.cfg in U-Boot source code for the list of available
+	  naming. See boards.cfg in U-Boot source code for the list of
-	  configurations.
+	  available configurations.
 endif
 
 choice
@@ -79,8 +79,8 @@ config BR2_TARGET_UBOOT_CUSTOM_REPO_VERSION
 	default BR2_TARGET_UBOOT_CUSTOM_GIT_VERSION \
 		if BR2_TARGET_UBOOT_CUSTOM_GIT_VERSION != ""  # legacy
 	help
-	  Revision to use in the typical format used by Git/Mercurial/Subversion
+	  Revision to use in the typical format used by
-	  E.G. a sha id, a tag, branch, ..
+	  Git/Mercurial/Subversion E.G. a sha id, a tag, branch, ..
 
 endif
 
@@ -229,25 +229,25 @@ config BR2_TARGET_UBOOT_FORMAT_NAND
 	bool "u-boot.nand (Freescale i.MX28)"
 	depends on BR2_arm
 	help
-	  This is Freescale i.MX28 BootStream format (.sb), with a header
+	  This is Freescale i.MX28 BootStream format (.sb), with a
-	  for booting from a NAND flash.
+	  header for booting from a NAND flash.
 
 	  U-boot includes an mxsboot tool to generate this format,
 	  starting from 2011.12.
 
-	  There are two possibilities when preparing an image writable to
+	  There are two possibilities when preparing an image writable
-	  NAND flash:
+	  to NAND flash:
-	  1) The NAND was not written at all yet or the BCB (Boot Control
+	  1) The NAND was not written at all yet or the BCB (Boot
-	  Blocks) is broken. In this case, the NAND image 'u-boot.nand'
+	  Control Blocks) is broken. In this case, the NAND image
-	  needs to written.
+	  'u-boot.nand' needs to written.
 	  2) The NAND flash was already written with a good BCB. This
 	  applies after 'u-boot.nand' was correctly written. There is no
-	  need to write the BCB again. In this case, the bootloader can be
+	  need to write the BCB again. In this case, the bootloader can
-	  upgraded by writing 'u-boot.sb'.
+	  be upgraded by writing 'u-boot.sb'.
 
 	  To satisfy both cases, the 'u-boot.nand' image obtained from
-	  mxsboot as well as the U-Boot make target 'u-boot.sb' are copied
+	  mxsboot as well as the U-Boot make target 'u-boot.sb' are
-	  to the binaries directory.
+	  copied to the binaries directory.
 
 	  See doc/README.mxs (or doc/README.mx28_common before 2013.07)
 
@@ -295,7 +295,8 @@ config BR2_TARGET_UBOOT_FORMAT_CUSTOM_NAME
 	depends on BR2_TARGET_UBOOT_FORMAT_CUSTOM
 	help
 	  In case the U-Boot binary for the target platform is not among
-	  the default names, one or more custom names can be listed here.
+	  the default names, one or more custom names can be listed
+	  here.
 	  Use space to separate multiple names.
 	  Example:
 	  u-boot_magic.bin