Documentation/boards/: Numerous grammar/typo/rendering fixes.

Various fixes related to fonts, rendering, grammar, etc., such as:

* spelling mistakes
* hyphenation
* capitalization for proper names
* proper bullet list formatting
* sentence structure

and so on.

Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

1 files changed, 18 insertions, 17 deletions

diff --git a/Documentation/boards/imx.rst b/Documentation/boards/imx.rst
index c6b208728e..0fde3e747e 100644
--- a/Documentation/boards/imx.rst
+++ b/Documentation/boards/imx.rst
@@ -1,9 +1,9 @@
 Freescale i.MX
 ==============
 
-Freescale i.MX is traditionally very good supported under barebox.
-Depending on the SoC there are different Boot Modes supported. Older
-SoCs up to i.MX31 only support the external Boot Mode. Newer SoCs
+Freescale i.MX is traditionally very well supported under barebox.
+Depending on the SoC, there are different Boot Modes supported. Older
+SoCs up to i.MX31 support only the external Boot Mode. Newer SoCs
 can be configured for internal or external Boot Mode with the internal
 boot mode being the more popular mode. The i.MX23 and i.MX28, also
 known as i.MXs, are special. These SoCs have a completely different
@@ -20,10 +20,10 @@ The Internal Boot Mode is supported on:
 * i.MX53
 * i.MX6
 
-With the Internal Boot Mode the images contain a header which describes
-where the binary shall be loaded and started. Also these headers contain
-a so called DCD table which consists of register/value pairs. These are
-executed by the Boot ROM and are used to configure the SDRAM. In barebox
+With the Internal Boot Mode, the images contain a header which describes
+where the binary shall be loaded and started. These headers also contain
+a so-called DCD table which consists of register/value pairs. These are
+executed by the Boot ROM and are used to configure the SDRAM. In barebox,
 the i.MX images are generated with the ``scripts/imx/imx-image`` tool.
 Normally it's not necessary to call this tool manually, it is executed
 automatically at the end of the build process.
@@ -36,8 +36,9 @@ SD card::
   # otherwise:
   cat barebox-flash-image > /dev/sdd
 
-This will overwrite the partition table on the card. It can be preserved
-with::
+The above will overwrite the MBR (and consequently the partition table)
+on the destination SD card. To preserve the MBR while writing the rest
+of the image to the card, use::
 
   dd if=images/barebox-freescale-imx51-babbage.img of=/dev/sdd bs=512 skip=1 seek=1
 
@@ -50,10 +51,10 @@ USB Boot
 
 Most boards can be explicitly configured for USB Boot Mode or fall back
 to USB Boot when no other medium can be found. The barebox repository
-contains a USB upload tool. As it depends on the libusb development headers
+contains a USB upload tool. As it depends on the libusb development headers,
 it is not built by default. Enable it explicitly in ``make menuconfig``
-and install the libusb development package. On Debian this can be done
-with ``apt-get install libusb-dev``. After compilation the tool can be used
+and install the libusb development package. On Debian, this can be done
+with ``apt-get install libusb-dev``. After compilation, the tool can be used
 with only the image name as argument::
 
   scripts/imx/imx-usb-loader images/barebox-freescale-imx51-babbage.img
@@ -68,13 +69,13 @@ The External Boot Mode is supported by the older i.MX SoCs:
 * i.MX27
 * i.MX31
 
-(It may be supported on newer SoCs aswell, but it is not widely used there)
+(It may be supported on newer SoCs as well, but it is not widely used there.)
 
-The External Boot Mode only supports booting from NOR and NAND flash. On NOR
-flash the binary is started directly on its physical address in memory. Booting
+The External Boot Mode supports booting only from NOR and NAND flash. On NOR
+flash, the binary is started directly on its physical address in memory. Booting
 from NAND flash is more complicated. The NAND flash controller copies the first
-2kb of the image to the NAND Controllers internal SRAM. This initial binary
-portion is then has to:
+2kb of the image to the NAND Controller's internal SRAM. This initial binary
+portion then has to:
 
 * Set up the SDRAM
 * Copy the initial binary to SDRAM to make the internal SRAM in the NAND flash