Fix spelling: pathes -> paths

Signed-off-by: Wadim Egorov <w.egorov@phytec.de>
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

3 files changed, 10 insertions, 10 deletions

diff --git a/Documentation/boards/efi.rst b/Documentation/boards/efi.rst
index 2147cb63db..b7ad40e472 100644
--- a/Documentation/boards/efi.rst
+++ b/Documentation/boards/efi.rst
@@ -164,20 +164,20 @@ Care must be taken that a partition is only accessed either via the Block IO Pro
 the File IO Interface. Doing both at the same time will most likely result in data
 corruption on the partition
 
-EFI device pathes
------------------
+EFI device paths
+----------------
 
-In EFI each device can be pointed to using a device path. Device pathes have multiple
+In EFI each device can be pointed to using a device path. Device paths have multiple
 components. The toplevel component on X86 systems will be the PCI root complex, on
 other systems this can be the physical memory space. Each component will now descrive
 how to find the child component on the parent bus. Additional device path nodes can
-describe network addresses or filenames on partitions. Device pathes have a binary
+describe network addresses or filenames on partitions. Device paths have a binary
 representation and a clearly defined string representation. These characteristics make
-device pathes suitable for describing boot entries. barebox could use device pathes
-to store the reference to kernels on boot media. Also device pathes could be used to
+device paths suitable for describing boot entries. barebox could use device paths
+to store the reference to kernels on boot media. Also device paths could be used to
 pass a root filesystem to the Kernel.
 
-Currently device pathes are only integrated into barebox in a way that each EFI device
+Currently device paths are only integrated into barebox in a way that each EFI device
 has a device parameter ``devpath`` which contains its device path:
 
 .. code-block:: sh
diff --git a/Documentation/user/booting-linux.rst b/Documentation/user/booting-linux.rst
index 17427f3636..3a8da11fd5 100644
--- a/Documentation/user/booting-linux.rst
+++ b/Documentation/user/booting-linux.rst
@@ -166,7 +166,7 @@ A Bootloader Spec Entry consists of key value pairs::
   linux      /6a9857a393724b7a981ebb5b8495b9ea/3.8.0-2.fc19.x86_64/linux
   initrd     /6a9857a393724b7a981ebb5b8495b9ea/3.8.0-2.fc19.x86_64/initrd
 
-All pathes are absolute pathes in the partition. Bootloader Spec Entries can
+All paths are absolute paths in the partition. Bootloader Spec Entries can
 be created manually, but there also is the ``scripts/kernel-install`` tool to
 create/list/modify entries directly on a MMC/SD card or other media. To use
 it create a SD card / USB memory stick with a /boot partition with type 0xea.
@@ -246,7 +246,7 @@ link target is exported from the server.
 
 ``boot net`` will then start the Kernel.
 
-If the pathes or names are not suitable they can be adjusted in
+If the paths or names are not suitable they can be adjusted in
 ``/env/boot/net``:
 
 .. code-block:: sh
diff --git a/Documentation/user/variables.rst b/Documentation/user/variables.rst
index ea99eb6113..0abc25d98a 100644
--- a/Documentation/user/variables.rst
+++ b/Documentation/user/variables.rst
@@ -79,7 +79,7 @@ of all variables with special meaning along with a short description::
 
   barebox:/ magicvar
   OPTARG                           optarg for hush builtin getopt
-  PATH                             colon separated list of pathes to search for executables
+  PATH                             colon separated list of paths to search for executables
   PS1                              hush prompt
   armlinux_architecture            ARM machine ID
   armlinux_system_rev              ARM system revision