[NET]: The scheduled removal of the frame diverter.

[linux-2.6] / Documentation / networking / slicecom.txt

diff --git a/Documentation/networking/slicecom.txt b/Documentation/networking/slicecom.txt
index 5fb21d5d46f03392734b733151cd97bc8686de1b..32d3b916afadfe19718ce5f00ffd436a97481402 100644 (file)
--- a/Documentation/networking/slicecom.txt
+++ b/Documentation/networking/slicecom.txt
@@ -126,7 +126,7 @@ comx0/boardnum      - board number of the SliceCom in the PC (using the 'natural'
 
 Though the options below are to be set on a single interface, they apply to the
 whole board. The restriction, to use them on 'UP' interfaces, is because the 
-command sequence below could lead to unpredicable results.
+command sequence below could lead to unpredictable results.
 
        # echo 0        >boardnum
        # echo internal >clock_source
@@ -262,7 +262,7 @@ which begin with '//' are the comments.
 //     initialised.
 // AUXP - Auxiliary Pattern Indication - 01010101.. received.
 // LFA  - Loss of Frame Alignment - no frame sync received.
-// RRA  - Receive Remote Alarm - the remote end's OK, but singnals error cond.
+// RRA  - Receive Remote Alarm - the remote end's OK, but signals error cond.
 // LMFA - Loss of CRC4 Multiframe Alignment - no CRC4 multiframe sync.
 // NMF  - No Multiframe alignment Found after 400 msec - no such alarm using
 //     no-crc4 or crc4 framing, see below.
@@ -364,6 +364,6 @@ Treat them very carefully, these can cause much trouble!
 
        # echo >lbireg 0x1d 0x21
 
-               - Swithing the loop off:
+               - Switching the loop off:
 
        # echo >lbireg 0x1d 0x00