Date:	Thu, 28 Apr 2016 04:39:45 +0900
From:	Kyeongmin Cho <korea.drzix@...il.com>
To:	Jonathan Corbet <corbet@....net>
Cc:	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	Kyeongmin Cho <korea.drzix@...il.com>
Subject: [PATCH] Documentation: Fix typos on several lines

There are many lines containing incorrect spelling words and needless spaces.
They should be fixed.

Signed-off-by: Kyeongmin Cho <korea.drzix@...il.com>
---
 Documentation/cpu-hotplug.txt       |  2 +-
 Documentation/devices.txt           |  4 ++--
 Documentation/hsi.txt               |  2 +-
 Documentation/kasan.txt             |  2 +-
 Documentation/kernel-parameters.txt |  4 ++--
 Documentation/lzo.txt               |  4 ++--
 Documentation/md.txt                | 24 ++++++++++++------------
 Documentation/module-signing.txt    |  2 +-
 Documentation/ramoops.txt           |  2 +-
 Documentation/robust-futexes.txt    |  4 ++--
 Documentation/static-keys.txt       |  2 +-
 Documentation/xillybus.txt          |  2 +-
 12 files changed, 27 insertions(+), 27 deletions(-)

diff --git a/Documentation/cpu-hotplug.txt b/Documentation/cpu-hotplug.txt
index dd68821..12e0b8f 100644
--- a/Documentation/cpu-hotplug.txt
+++ b/Documentation/cpu-hotplug.txt
@@ -97,7 +97,7 @@ from the map depending on the event is hot-add/hot-remove. There are currently
 no locking rules as of now. Typical usage is to init topology during boot,
 at which time hotplug is disabled.
 
-You really dont need to manipulate any of the system cpu maps. They should
+You really don't need to manipulate any of the system cpu maps. They should
 be read-only for most use. When setting up per-cpu resources almost always use
 cpu_possible_mask/for_each_possible_cpu() to iterate.
 
diff --git a/Documentation/devices.txt b/Documentation/devices.txt
index 87b4c5e..e036e4f 100644
--- a/Documentation/devices.txt
+++ b/Documentation/devices.txt
@@ -400,7 +400,7 @@ Your cooperation is appreciated.
 		182 = /dev/perfctr	Performance-monitoring counters
 		183 = /dev/hwrng	Generic random number generator
 		184 = /dev/cpu/microcode CPU microcode update interface
-		186 = /dev/atomicps	Atomic shapshot of process state data
+		186 = /dev/atomicps	Atomic snapshot of process state data
 		187 = /dev/irnet	IrNET device
 		188 = /dev/smbusbios	SMBus BIOS
 		189 = /dev/ussp_ctl	User space serial port control
@@ -2947,7 +2947,7 @@ Your cooperation is appreciated.
 		  2 = /dev/dvb/adapter0/sec0      (obsolete/unused)
 		  3 = /dev/dvb/adapter0/frontend0 first frontend device of first card
 		  4 = /dev/dvb/adapter0/demux0    first demux device of first card
-		  5 = /dev/dvb/adapter0/dvr0      first digital video recoder device of first card
+		  5 = /dev/dvb/adapter0/dvr0      first digital video recorder device of first card
 		  6 = /dev/dvb/adapter0/ca0       first common access port of first card
 		  7 = /dev/dvb/adapter0/net0      first network device of first card
 		  8 = /dev/dvb/adapter0/osd0      first on-screen-display device of first card
diff --git a/Documentation/hsi.txt b/Documentation/hsi.txt
index 6ac6cd5..bf0bcbe 100644
--- a/Documentation/hsi.txt
+++ b/Documentation/hsi.txt
@@ -49,7 +49,7 @@ use an arbitrary number of channels.
 ~~~~~~~~~~~~~~~~~~
 
 Each port automatically registers a generic client driver called hsi_char,
-which provides a charecter device for userspace representing the HSI port.
+which provides a character device for userspace representing the HSI port.
 It can be used to communicate via HSI from userspace. Userspace may
 configure the hsi_char device using the following ioctl commands:
 
diff --git a/Documentation/kasan.txt b/Documentation/kasan.txt
index 7dd95b3..912ef93 100644
--- a/Documentation/kasan.txt
+++ b/Documentation/kasan.txt
@@ -116,7 +116,7 @@ Memory state around the buggy address:
  ffff8800693bc800: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
 ==================================================================
 
-The header of the report discribe what kind of bug happened and what kind of
+The header of the report describes what kind of bug happened and what kind of
 access caused it. It's followed by the description of the accessed slub object
 (see 'SLUB Debug output' section in Documentation/vm/slub.txt for details) and
 the description of the accessed memory page.
diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
index 0b3de80..e7f2051 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -1542,7 +1542,7 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
 
 	ima_policy=	[IMA]
 			The builtin measurement policy to load during IMA
-			setup.  Specyfing "tcb" as the value, measures all
+			setup.  Specifying "tcb" as the value, measures all
 			programs exec'd, files mmap'd for exec, and all files
 			opened with the read mode bit set by either the
 			effective uid (euid=0) or uid=0.
@@ -3984,7 +3984,7 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
 			See also Documentation/input/joystick-parport.txt
 
 	udbg-immortal	[PPC] When debugging early kernel crashes that
-			happen after console_init() and before a proper 
+			happen after console_init() and before a proper
 			console driver takes over, this boot options might
 			help "seeing" what's going on.
 
diff --git a/Documentation/lzo.txt b/Documentation/lzo.txt
index ea45dd3..285c54f 100644
--- a/Documentation/lzo.txt
+++ b/Documentation/lzo.txt
@@ -69,9 +69,9 @@ Description
 
   IMPORTANT NOTE : in the code some length checks are missing because certain
   instructions are called under the assumption that a certain number of bytes
-  follow because it has already been garanteed before parsing the instructions.
+  follow because it has already been guaranteed before parsing the instructions.
   They just have to "refill" this credit if they consume extra bytes. This is
-  an implementation design choice independant on the algorithm or encoding.
+  an implementation design choice independent on the algorithm or encoding.
 
 Byte sequences
 
diff --git a/Documentation/md.txt b/Documentation/md.txt
index 1a2ada4..7b08a3e 100644
--- a/Documentation/md.txt
+++ b/Documentation/md.txt
@@ -1,5 +1,5 @@
 Tools that manage md devices can be found at
-   http://www.kernel.org/pub/linux/utils/raid/ 
+   http://www.kernel.org/pub/linux/utils/raid/
 
 
 Boot time assembly of RAID arrays
@@ -15,9 +15,9 @@ for raid arrays with persistent superblocks
   md=<md device no.>,dev0,dev1,...,devn
 or, to assemble a partitionable array:
   md=d<md device no.>,dev0,dev1,...,devn
-  
-md device no. = the number of the md device ... 
-              0 means md0, 
+
+md device no. = the number of the md device ...
+              0 means md0,
 	      1 md1,
 	      2 md2,
 	      3 md3,
@@ -29,11 +29,11 @@ raid level = -1 linear mode
 
 chunk size factor = (raid-0 and raid-1 only)
               Set  the chunk size as 4k << n.
-	      
+
 fault level = totally ignored
-			    
+
 dev0-devn: e.g. /dev/hda1,/dev/hdc1,/dev/sda1,/dev/sdb1
-			    
+
 A possible loadlin line (Harald Hoyer <HarryH@...al.Net>)  looks like this:
 
 e:\loadlin\loadlin e:\zimage root=/dev/md0 md=0,0,4,0,/dev/hdb2,/dev/hdc3 ro
@@ -273,7 +273,7 @@ All md devices contain:
          When written, doesn't tear down array, but just stops it
      suspended (not supported yet)
          All IO requests will block. The array can be reconfigured.
-         Writing this, if accepted, will block until array is quiessent
+         Writing this, if accepted, will block until array is quiescent
      readonly
          no resync can happen.  no superblocks get written.
          write requests fail
@@ -338,9 +338,9 @@ All md devices contain:
      When metadata is managed externally, it should be set to true
      once the array becomes non-degraded, and this fact has been
      recorded in the metadata.
-     
-     
-     
+
+
+
 
 As component devices are added to an md array, they appear in the 'md'
 directory as new directories named
@@ -451,7 +451,7 @@ Each directory contains:
 
 	Setting this to 'none' is equivalent to setting 'in_sync'.
 	Setting to any other value also clears the 'in_sync' flag.
-	
+
       bad_blocks
 	This gives the list of all known bad blocks in the form of
 	start address and length (in sectors respectively). If output
diff --git a/Documentation/module-signing.txt b/Documentation/module-signing.txt
index 696d5ca..b189b94 100644
--- a/Documentation/module-signing.txt
+++ b/Documentation/module-signing.txt
@@ -101,7 +101,7 @@ This has a number of options available:
      certificate and a private key.
 
      If the PEM file containing the private key is encrypted, or if the
-     PKCS#11 token requries a PIN, this can be provided at build time by
+     PKCS#11 token requires a PIN, this can be provided at build time by
      means of the KBUILD_SIGN_PIN variable.
 
 
diff --git a/Documentation/ramoops.txt b/Documentation/ramoops.txt
index 5d86756..dca9c61 100644
--- a/Documentation/ramoops.txt
+++ b/Documentation/ramoops.txt
@@ -19,7 +19,7 @@ and type of the memory area are set using three variables:
   * "mem_address" for the start
   * "mem_size" for the size. The memory size will be rounded down to a
   power of two.
-  * "mem_type" to specifiy if the memory type (default is pgprot_writecombine).
+  * "mem_type" to specify if the memory type (default is pgprot_writecombine).
 
 Typically the default value of mem_type=0 should be used as that sets the pstore
 mapping to pgprot_writecombine. Setting mem_type=1 attempts to use
diff --git a/Documentation/robust-futexes.txt b/Documentation/robust-futexes.txt
index af6fce2..31f68b8 100644
--- a/Documentation/robust-futexes.txt
+++ b/Documentation/robust-futexes.txt
@@ -126,9 +126,9 @@ vma based method:
 
  - no VM changes are needed - 'struct address_space' is left alone.
 
- - no registration of individual locks is needed: robust mutexes dont
+ - no registration of individual locks is needed: robust mutexes don't
    need any extra per-lock syscalls. Robust mutexes thus become a very
-   lightweight primitive - so they dont force the application designer
+   lightweight primitive - so they don't force the application designer
    to do a hard choice between performance and robustness - robust
    mutexes are just as fast.
 
diff --git a/Documentation/static-keys.txt b/Documentation/static-keys.txt
index 477927b..f73a43d 100644
--- a/Documentation/static-keys.txt
+++ b/Documentation/static-keys.txt
@@ -116,7 +116,7 @@ Or:
 
 Keys defined via DEFINE_STATIC_KEY_TRUE(), or DEFINE_STATIC_KEY_FALSE, may
 be used in either static_branch_likely() or static_branch_unlikely()
-statemnts.
+statements.
 
 Branch(es) can be set true via:
 
diff --git a/Documentation/xillybus.txt b/Documentation/xillybus.txt
index 81d111b..1660145 100644
--- a/Documentation/xillybus.txt
+++ b/Documentation/xillybus.txt
@@ -215,7 +215,7 @@ in xillybus_core.c as follows:
   choice is a non-zero value, to match standard UNIX behavior.
 
 * synchronous: A non-zero value means that the pipe is synchronous. See
-  Syncronization above.
+  Synchronization above.
 
 * bufsize: Each DMA buffer's size. Always a power of two.
 
-- 
2.5.5

Powered by blists - more mailing lists