[PATCH v4 11/11] doc: develop: orthographic delights

[Lothar Rubusch]

Fix some typos and duplicate words in documentation files.

Signed-off-by: Lothar Rubusch <l.rubusch at gmail.com>
---
 doc/develop/gdb.rst      |  2 +-
 tools/binman/binman.rst  |  4 ++--
 tools/binman/entries.rst | 22 +++++++++++-----------
 3 files changed, 14 insertions(+), 14 deletions(-)

diff --git a/doc/develop/gdb.rst b/doc/develop/gdb.rst
index 4e359c7f22..ebe65492ef 100644
--- a/doc/develop/gdb.rst
+++ b/doc/develop/gdb.rst
@@ -13,7 +13,7 @@ Similarly QEMU can provide a GDB server.
 Preparing build
 ---------------
 
-Building U-Boot with with reduced optimization (-Og) and without link time
+Building U-Boot with reduced optimization (-Og) and without link time
 optimization is recommended for easier debugging::
 
     CONFIG_CC_OPTIMIZE_FOR_DEBUG=y
diff --git a/tools/binman/binman.rst b/tools/binman/binman.rst
index 381e55686f..df682ba86d 100644
--- a/tools/binman/binman.rst
+++ b/tools/binman/binman.rst
@@ -1047,8 +1047,8 @@ Here, a new 'value' property will be written to the 'hash' node containing
 the hash of the 'u-boot' entry. Only SHA256 is supported at present. Whole
 sections can be hased if desired, by adding the 'hash' node to the section.
 
-The has value can be chcked at runtime by hashing the data actually read and
-comparing this has to the value in the device tree.
+The hash value can be checked at runtime by hashing the data actually read and
+comparing this hash to the value in the device tree.
 
 
 Expanded entries
diff --git a/tools/binman/entries.rst b/tools/binman/entries.rst
index e918162fb4..79d93eb22d 100644
--- a/tools/binman/entries.rst
+++ b/tools/binman/entries.rst
@@ -240,7 +240,7 @@ Properties / Entry arguments:
         lz4: Use lz4 compression (via 'lz4' command-line utility)
 
 This entry reads data from a file and places it in the entry. The
-default filename is often specified specified by the subclass. See for
+default filename is often specified by the subclass. See for
 example the 'u-boot' entry which provides the filename 'u-boot.bin'.
 
 If compression is enabled, an extra 'uncomp-size' property is written to
@@ -286,7 +286,7 @@ Entry: blob-ext-list: List of externally built binary blobs
 This is like blob-ext except that a number of blobs can be provided,
 typically with some sort of relationship, e.g. all are DDC parameters.
 
-If any of the external files needed by this llist is missing, binman can
+If any of the external files needed by this list is missing, binman can
 optionally ignore it and produce a broken image with a warning.
 
 Args:
@@ -1164,7 +1164,7 @@ Properties / Entry arguments:
 
 FMAP is a simple format used by flashrom, an open-source utility for
 reading and writing the SPI flash, typically on x86 CPUs. The format
-provides flashrom with a list of areas, so it knows what it in the flash.
+provides flashrom with a list of areas, that it knows what is in the flash.
 It can then read or write just a single area, instead of the whole flash.
 
 The format is defined by the flashrom project, in the file lib/fmap.h -
@@ -1338,7 +1338,7 @@ Properties / Entry arguments:
 This file contains a binary blob which is used on some devices to set up
 the silicon. U-Boot executes this code in U-Boot proper after SDRAM is
 running, so that it can make full use of memory. Documentation is typically
-not available in sufficient detail to allow U-Boot do this this itself.
+not available in sufficient detail to allow U-Boot do this itself.
 
 An example filename is 'fsp_s.bin'
 
@@ -1411,7 +1411,7 @@ Properties / Entry arguments:
 This file contains code used by the SoC that is required to make it work.
 The Management Engine is like a background task that runs things that are
 not clearly documented, but may include keyboard, display and network
-access. For platform that use ME it is not possible to disable it. U-Boot
+access. For platforms using ME, it is not possible to disable it. U-Boot
 does not directly execute code in the ME binary.
 
 A typical filename is 'me.bin'.
@@ -2303,8 +2303,8 @@ to avoid the data overlapping with U-Boot variables. This entry is useful in
 that case. It automatically pads out the entry size to cover both the code,
 data and BSS.
 
-The contents of this entry will a certain number of zero bytes, determined
-by __bss_size
+The contents of this entry will be filled up with a number of zero bytes,
+determined by __bss_size
 
 The ELF file 'spl/u-boot-spl' must also be available for this to work, since
 binman uses that to look up the BSS address.
@@ -2479,8 +2479,8 @@ to avoid the data overlapping with U-Boot variables. This entry is useful in
 that case. It automatically pads out the entry size to cover both the code,
 data and BSS.
 
-The contents of this entry will a certain number of zero bytes, determined
-by __bss_size
+The contents of this entry will be filled up with a number of zero bytes,
+determined by __bss_size
 
 The ELF file 'tpl/u-boot-tpl' must also be available for this to work, since
 binman uses that to look up the BSS address.
@@ -2678,8 +2678,8 @@ to avoid the data overlapping with U-Boot variables. This entry is useful in
 that case. It automatically pads out the entry size to cover both the code,
 data and BSS.
 
-The contents of this entry will a certain number of zero bytes, determined
-by __bss_size
+The contents of this entry will be filled up with a number of zero bytes,
+determined by __bss_size
 
 The ELF file 'vpl/u-boot-vpl' must also be available for this to work, since
 binman uses that to look up the BSS address.
-- 
2.25.1