diff options
| author | Matt LaPlante <kernel1@cyberdogtech.com> | 2006-10-03 22:49:15 +0200 |
|---|---|---|
| committer | Adrian Bunk <bunk@stusta.de> | 2006-10-03 22:49:15 +0200 |
| commit | a2ffd2751683f4275d4d1aa5ce37e5a6a1ae21df (patch) | |
| tree | 81d772c66b92c87e585dde45f89b91904055471b /Documentation/s390 | |
| parent | fff9289b219f48cb2296714fea3d71f516991f9f (diff) | |
| download | linux-a2ffd2751683f4275d4d1aa5ce37e5a6a1ae21df.tar.gz linux-a2ffd2751683f4275d4d1aa5ce37e5a6a1ae21df.tar.bz2 linux-a2ffd2751683f4275d4d1aa5ce37e5a6a1ae21df.zip | |
Fix typos in Documentation/: 'F'-'G'
This patch fixes typos in various Documentation txts. The patch addresses
some words starting with the letters 'F'-'G'.
Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Diffstat (limited to 'Documentation/s390')
| -rw-r--r-- | Documentation/s390/Debugging390.txt | 2 | ||||
| -rw-r--r-- | Documentation/s390/s390dbf.txt | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/s390/Debugging390.txt b/Documentation/s390/Debugging390.txt index ffb74a1656e6..248953a2574b 100644 --- a/Documentation/s390/Debugging390.txt +++ b/Documentation/s390/Debugging390.txt @@ -88,7 +88,7 @@ s/390 z/Architecture 0 0 Reserved ( must be 0 ) otherwise specification exception occurs. 1 1 Program Event Recording 1 PER enabled, - PER is used to facilititate debugging e.g. single stepping. + PER is used to facilitate debugging e.g. single stepping. 2-4 2-4 Reserved ( must be 0 ). diff --git a/Documentation/s390/s390dbf.txt b/Documentation/s390/s390dbf.txt index 5ff6fe551b93..2095a2704b8f 100644 --- a/Documentation/s390/s390dbf.txt +++ b/Documentation/s390/s390dbf.txt @@ -11,7 +11,7 @@ where log records can be stored efficiently in memory, where each component (e.g. device drivers) can have one separate debug log. One purpose of this is to inspect the debug logs after a production system crash in order to analyze the reason for the crash. -If the system still runs but only a subcomponent which uses dbf failes, +If the system still runs but only a subcomponent which uses dbf fails, it is possible to look at the debug logs on a live system via the Linux debugfs filesystem. The debug feature may also very useful for kernel and driver development. |