X-Git-Url: https://git.karo-electronics.de/?a=blobdiff_plain;f=Documentation%2FCodingStyle;h=8bb37237ebd25b19759cc47874c63155406ea28f;hb=312cec5d094a5d4e68434ace4c5cb55e4f8dfee5;hp=72968cd5eaf3286f08cc6eb7dfb3115ff9c5ce90;hpb=e0d2054fd3cf167395390dc1758644486c782707;p=karo-tx-linux.git

diff --git a/Documentation/CodingStyle b/Documentation/CodingStyle
index 72968cd5eaf3..8bb37237ebd2 100644
--- a/Documentation/CodingStyle
+++ b/Documentation/CodingStyle
@@ -698,8 +698,8 @@ very often is not. Abundant use of the inline keyword leads to a much bigger
 kernel, which in turn slows the system as a whole down, due to a bigger
 icache footprint for the CPU and simply because there is less memory
 available for the pagecache. Just think about it; a pagecache miss causes a
-disk seek, which easily takes 5 miliseconds. There are a LOT of cpu cycles
-that can go into these 5 miliseconds.
+disk seek, which easily takes 5 milliseconds. There are a LOT of cpu cycles
+that can go into these 5 milliseconds.
 
 A reasonable rule of thumb is to not put inline at functions that have more
 than 3 lines of code in them. An exception to this rule are the cases where