diff --git a/Documentation/ABI/README b/Documentation/ABI/README
index 1fafc4b0753b4e..9f9cde5751bea2 100644
--- a/Documentation/ABI/README
+++ b/Documentation/ABI/README
@@ -1,6 +1,6 @@
 This directory attempts to document the ABI between the Linux kernel and
 userspace, and the relative stability of these interfaces.  Due to the
-everchanging nature of Linux, and the differing maturity levels, these
+ever-changing nature of Linux, and the differing maturity levels, these
 interfaces should be used by userspace programs in different ways.
 
 We have four different levels of ABI stability, as shown by the four
diff --git a/Documentation/crypto/asymmetric-keys.txt b/Documentation/crypto/asymmetric-keys.txt
index b7675904a7478a..18d536563be844 100644
--- a/Documentation/crypto/asymmetric-keys.txt
+++ b/Documentation/crypto/asymmetric-keys.txt
@@ -33,7 +33,7 @@ merely be an interface to the TPM driver.
 
 Also provided is the concept of a data parser.  Data parsers are responsible
 for extracting information from the blobs of data passed to the instantiation
-function.  The first data parser that recognises the blob gets to set the
+function.  The first data parser that recognizes the blob gets to set the
 subtype of the key and define the operations that can be done on that key.
 
 A data parser may interpret the data blob as containing the bits representing a
@@ -166,7 +166,7 @@ Asymmetric keys have a subtype that defines the set of operations that can be
 performed on that key and that determines what data is attached as the key
 payload.  The payload format is entirely at the whim of the subtype.
 
-The subtype is selected by the key data parser and the parser must initialise
+The subtype is selected by the key data parser and the parser must initialize
 the data required for it.  The asymmetric key retains a reference on the
 subtype module.
 
@@ -279,13 +279,13 @@ mandatory:
      The instantiation data is in a blob pointed to by data and is datalen in
      size.  The parse() function is not permitted to change these two values at
      all, and shouldn't change any of the other values _unless_ they are
-     recognise the blob format and will not return -EBADMSG to indicate it is
+     recognize the blob format and will not return -EBADMSG to indicate it is
      not theirs.
 
      If the parser is happy with the blob, it should propose a description for
      the key and attach it to ->description, ->type_data[0] should be set to
      point to the subtype to be used, ->payload should be set to point to the
-     initialised data for that subtype, ->type_data[1] should point to a hex
+     initialized data for that subtype, ->type_data[1] should point to a hex
      fingerprint and quotalen should be updated to indicate how much quota this
      key should account for.
 
@@ -295,8 +295,8 @@ mandatory:
      the subtype pointed to by ->type_data[0] will be put.
 
 
-     If the data format is not recognised, -EBADMSG should be returned.  If it
-     is recognised, but the key cannot for some reason be set up, some other
+     If the data format is not recognized, -EBADMSG should be returned.  If it
+     is recognized, but the key cannot for some reason be set up, some other
      negative error code should be returned.  On success, 0 should be returned.
 
      The key's fingerprint string may be partially matched upon.  For a
diff --git a/Documentation/gpio/gpio-legacy.txt b/Documentation/gpio/gpio-legacy.txt
index 6f83fa965b4b6e..bbf5cd966a6482 100644
--- a/Documentation/gpio/gpio-legacy.txt
+++ b/Documentation/gpio/gpio-legacy.txt
@@ -726,7 +726,7 @@ read-only attributes:
 
     	"label" ... provided for diagnostics (not always unique)
 
-    	"ngpio" ... how many GPIOs this manges (N to N + ngpio - 1)
+    	"ngpio" ... how many GPIOs this manages (N to N + ngpio - 1)
 
 Board documentation should in most cases cover what GPIOs are used for
 what purposes.  However, those numbers are not always stable; GPIOs on
@@ -769,7 +769,7 @@ use this to provide the interface under their own device in sysfs with
 a descriptive name.
 
 Drivers can use gpio_sysfs_set_active_low() to hide GPIO line polarity
-differences between boards from user space.  This only affects the
+differences between boards from userspace.  This only affects the
 sysfs interface.  Polarity change can be done both before and after
 gpio_export(), and previously enabled poll(2) support for either
 rising or falling edge will be reconfigured to follow this setting.
diff --git a/Documentation/gpio/sysfs.txt b/Documentation/gpio/sysfs.txt
index c2c3a97f8ff7c2..55788da678341b 100644
--- a/Documentation/gpio/sysfs.txt
+++ b/Documentation/gpio/sysfs.txt
@@ -150,6 +150,6 @@ use this to provide the interface under their own device in sysfs with
 a descriptive name.
 
 Drivers can use gpiod_sysfs_set_active_low() to hide GPIO line polarity
-differences between boards from user space. Polarity change can be done both
+differences between boards from userspace. Polarity change can be done both
 before and after gpiod_export(), and previously enabled poll(2) support for
 either rising or falling edge will be reconfigured to follow this setting.