doc: Fix typos

Fix typos/wording in various files in doc/.

Signed-off-by: Wolfgang Wallner <[email protected]>
Reviewed-by: E Shattow <[email protected]>

3 files changed, 9 insertions, 9 deletions

diff --git a/doc/usage/environment.rst b/doc/usage/environment.rst
index 5553a629e42..0143f81f2c0 100644
--- a/doc/usage/environment.rst
+++ b/doc/usage/environment.rst
@@ -213,7 +213,7 @@ updatefile
 
 autoload
     if set to "no" (any string beginning with 'n'),
-    "bootp" and "dhcp" will just load perform a lookup of the
+    "bootp" and "dhcp" will just perform a lookup of the
     configuration from the BOOTP server, but not try to
     load any image.
 
diff --git a/doc/usage/fit/beaglebone_vboot.rst b/doc/usage/fit/beaglebone_vboot.rst
index 1298ba1ae08..b15399441ee 100644
--- a/doc/usage/fit/beaglebone_vboot.rst
+++ b/doc/usage/fit/beaglebone_vboot.rst
@@ -473,7 +473,7 @@ you sign::
 Here we are overriding the normal device tree file with our one, which
 contains the public key.
 
-Now you have a special U-Boot image with the public key. It can verify can
+Now you have a special U-Boot image with the public key. It can verify any
 kernel that you sign with the private key as in step 5.
 
 If you like you can take a look at the public key information that mkimage
diff --git a/doc/usage/fit/overlay-fdt-boot.rst b/doc/usage/fit/overlay-fdt-boot.rst
index d687e98ea2a..f5af6d9df05 100644
--- a/doc/usage/fit/overlay-fdt-boot.rst
+++ b/doc/usage/fit/overlay-fdt-boot.rst
@@ -19,7 +19,7 @@ Configuration without overlays
 ------------------------------
 
 Take a hypothetical board named 'foo' where there are different supported
-revisions, reva and revb. Assume that both board revisions can use add a bar
+revisions, reva and revb. Assume that both board revisions can add a bar
 add-on board, while only the revb board can use a baz add-on board.
 
 Without using overlays the configuration would be as follows for every case::
@@ -97,7 +97,7 @@ Without using overlays the configuration would be as follows for every case::
 	};
 
 Note the blob needs to be compiled for each case and the combinatorial explosion of
-configurations. A typical device tree blob is in the low hunderds of kbytes so a
+configurations. A typical device tree blob is in the low hundreds of kbytes so a
 multitude of configuration grows the image quite a bit.
 
 Booting this image is done by using::
@@ -117,7 +117,7 @@ Configuration using overlays
 ----------------------------
 
 Device tree overlays can be applied to a base DT and result in the same blob
-being passed to the booting kernel. This saves on space and avoid the combinatorial
+being passed to the booting kernel. This saves on space and avoids the combinatorial
 explosion problem::
 
     /dts-v1/;
@@ -164,7 +164,7 @@ explosion problem::
         };
 
         configurations {
-            default = "foo-reva.dtb;
+            default = "foo-reva.dtb";
             foo-reva.dtb {
                 kernel = "kernel";
                 fdt = "fdt-1", "fdt-2";
@@ -209,9 +209,9 @@ to be writeable.
 Configuration using overlays and feature selection
 --------------------------------------------------
 
-Although the configuration in the previous section works is a bit inflexible
-since it requires all possible configuration options to be laid out before
-hand in the FIT image. For the add-on boards the extra config selection method
+Although the configuration in the previous section works, it is a bit inflexible
+since it requires all possible configuration options to be laid out beforehand
+in the FIT image. For the add-on boards the extra config selection method
 might make sense.
 
 Note the two bar & baz configuration nodes. To boot a reva board with