X-Git-Url: https://err.no/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=Documentation%2Flocal_ops.txt;h=4269a1105b378fafcc689435a2531b9d9d4287db;hb=fbf4d7ffda0398e8b20aa8b34ca751bf946699ef;hp=a134a563db32224d292ba83a3ddb06ba7223b83c;hpb=74beb9db77930be476b267ec8518a642f39a04bf;p=linux-2.6

diff --git a/Documentation/local_ops.txt b/Documentation/local_ops.txt
index a134a563db..4269a1105b 100644
--- a/Documentation/local_ops.txt
+++ b/Documentation/local_ops.txt
@@ -27,7 +27,7 @@ CPU which owns the data. Therefore, care must taken to make sure that only one
 CPU writes to the local_t data. This is done by using per cpu data and making
 sure that we modify it from within a preemption safe context. It is however
 permitted to read local_t data from any CPU : it will then appear to be written
-out of order wrt other memory writes on the owner CPU.
+out of order wrt other memory writes by the owner CPU.
 
 
 * Implementation for a given architecture