summaryrefslogtreecommitdiffstats
path: root/Documentation/parisc
diff options
context:
space:
mode:
authorMasanari Iida <standby24x7@gmail.com>2012-04-09 17:22:13 +0200
committerJiri Kosina <jkosina@suse.cz>2012-04-16 14:37:13 +0200
commitc94bed8e1960587d3d93664b11ebf22677c1a541 (patch)
treee63acbfb5c6950c137f1b9d89ddc147c82188f23 /Documentation/parisc
parentscsi: fix comment spelling fix recory->recovery (diff)
downloadlinux-c94bed8e1960587d3d93664b11ebf22677c1a541.tar.xz
linux-c94bed8e1960587d3d93664b11ebf22677c1a541.zip
Documentation: Fix typo in multiple files in Documentation
Correct multiple spelling typo in Documentation. Signed-off-by: Masanari Iida <standby24x7@gmail.com> Acked-by: Rob Landley <rob@landley.net> Reported-by: Anders Larsen <al@alarsen.net> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'Documentation/parisc')
-rw-r--r--Documentation/parisc/debugging2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/parisc/debugging b/Documentation/parisc/debugging
index d728594058e5..7d75223fa18d 100644
--- a/Documentation/parisc/debugging
+++ b/Documentation/parisc/debugging
@@ -34,6 +34,6 @@ registers interruption handlers read to find out where the machine
was interrupted - so if you get an interruption between the instruction
that clears the Q bit and the RFI that sets it again you don't know
where exactly it happened. If you're lucky the IAOQ will point to the
-instrucion that cleared the Q bit, if you're not it points anywhere
+instruction that cleared the Q bit, if you're not it points anywhere
at all. Usually Q bit problems will show themselves in unexplainable
system hangs or running off the end of physical memory.