Merge tag 'edac_urgent_for_4.2' of git://git.kernel.org/pub/scm/linux/kernel/git...

[firefly-linux-kernel-4.4.55.git] / Documentation / workqueue.txt

diff --git a/Documentation/workqueue.txt b/Documentation/workqueue.txt
index f81a65b54c29e6f8d853e621fddd530eebf842a1..5e0e05c5183e290e8d78c531a3f42bc3c85377f7 100644 (file)
--- a/Documentation/workqueue.txt
+++ b/Documentation/workqueue.txt
@@ -365,7 +365,7 @@ root      5674  0.0  0.0      0     0 ?        S    12:13   0:00 [kworker/1:0]
 If kworkers are going crazy (using too much cpu), there are two types
 of possible problems:
 
-       1. Something beeing scheduled in rapid succession
+       1. Something being scheduled in rapid succession
        2. A single work item that consumes lots of cpu cycles
 
 The first one can be tracked using tracing: