X-Git-Url: http://drtracing.org/?a=blobdiff_plain;f=Documentation%2Fworkqueue.txt;h=5e0e05c5183e290e8d78c531a3f42bc3c85377f7;hb=5c755fe142b421d295e7dd64a9833c12abbfd28e;hp=f81a65b54c29e6f8d853e621fddd530eebf842a1;hpb=fbe43ff0031ded2b8500382da17d5d815a9c3edd;p=deliverable%2Flinux.git

diff --git a/Documentation/workqueue.txt b/Documentation/workqueue.txt
index f81a65b54c29..5e0e05c5183e 100644
--- 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: