summaryrefslogtreecommitdiffstats
path: root/Documentation/arm/README
diff options
context:
space:
mode:
authorAndrzej Zaborowski <balrogg@gmail.com>2006-03-24 18:13:37 +0100
committerAdrian Bunk <bunk@stusta.de>2006-03-24 18:13:37 +0100
commit13fce8062968996da496d4f65cc1c1f845704604 (patch)
treefa8f3e8ee813397d043efd81780c487531705aa1 /Documentation/arm/README
parenttabify drivers/char/Makefile (diff)
downloadlinux-13fce8062968996da496d4f65cc1c1f845704604.tar.xz
linux-13fce8062968996da496d4f65cc1c1f845704604.zip
Fix simple typos
This corrects some trivial errors in ARM docs and comments, Signed-off-by: Adrian Bunk <bunk@stusta.de>
Diffstat (limited to 'Documentation/arm/README')
-rw-r--r--Documentation/arm/README2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/arm/README b/Documentation/arm/README
index 5ed6f3530b86..9b9c8226fdc4 100644
--- a/Documentation/arm/README
+++ b/Documentation/arm/README
@@ -89,7 +89,7 @@ Modules
Although modularisation is supported (and required for the FP emulator),
each module on an ARM2/ARM250/ARM3 machine when is loaded will take
memory up to the next 32k boundary due to the size of the pages.
- Therefore, modularisation on these machines really worth it?
+ Therefore, is modularisation on these machines really worth it?
However, ARM6 and up machines allow modules to take multiples of 4k, and
as such Acorn RiscPCs and other architectures using these processors can