summaryrefslogtreecommitdiff
path: root/board
diff options
context:
space:
mode:
authorJeremiah Mahler <jmmahler@gmail.com>2015-01-06 16:40:28 -0800
committerTom Rini <trini@ti.com>2015-01-08 11:00:45 -0500
commitfa840b09216c6ea728240294b66d2d9ae42c36e1 (patch)
treea9caf608e71b9be6635729583b1cc09333201607 /board
parent8ed5e4ce0b9475f51f288409443b959b9a3a4f27 (diff)
downloadu-boot-imx-fa840b09216c6ea728240294b66d2d9ae42c36e1.zip
u-boot-imx-fa840b09216c6ea728240294b66d2d9ae42c36e1.tar.gz
u-boot-imx-fa840b09216c6ea728240294b66d2d9ae42c36e1.tar.bz2
doc: fix spelling errors in am335x/README
Fix several spelling errors and replace the invalid word "architectured" with "designed". Signed-off-by: Jeremiah Mahler <jmmahler@gmail.com>
Diffstat (limited to 'board')
-rw-r--r--board/ti/am335x/README6
1 files changed, 3 insertions, 3 deletions
diff --git a/board/ti/am335x/README b/board/ti/am335x/README
index 947305b..19e0ecc 100644
--- a/board/ti/am335x/README
+++ b/board/ti/am335x/README
@@ -86,9 +86,9 @@ Step-3: Set BOOTSEL pin to select NAND boot, and POR the device.
NOR
===
-The Beaglebone White can be equiped with a "memory cape" that in turn can
+The Beaglebone White can be equipped with a "memory cape" that in turn can
have a NOR module plugged into it. In this case it is then possible to
-program and boot from NOR. Note that due to how U-Boot is architectured we
+program and boot from NOR. Note that due to how U-Boot is designed we
must build a specific version of U-Boot that knows we have NOR flash. This
build is named 'am335x_evm_nor'. Further, we have a 'am335x_evm_norboot'
build that will assume that the environment is on NOR rather than NAND. In
@@ -193,7 +193,7 @@ Falcon Mode: NAND
In this case the additional data is written to another partition of the
NAND. In this example we assume that the uImage and device tree to be are
-already located on the NAND somewhere (such as fileystem or mtd partition)
+already located on the NAND somewhere (such as filesystem or mtd partition)
along with a Falcon Mode aware MLO written to the correct locations for
booting and mtdparts have been configured correctly for the board: