unified MX27, MX25, MX37 trees

[karo-tx-redboot.git] / packages / devs / eth / phy / v2_0 / doc / eth_phy.sgml

diff --git a/packages/devs/eth/phy/v2_0/doc/eth_phy.sgml b/packages/devs/eth/phy/v2_0/doc/eth_phy.sgml
index 4d4c9268d4d861a890332287d19d4cfb3b72b27a..35d61c97de0c5ed2ace06ebb00b8c8615de38e51 100644 (file)
--- a/packages/devs/eth/phy/v2_0/doc/eth_phy.sgml
+++ b/packages/devs/eth/phy/v2_0/doc/eth_phy.sgml
@@ -38,7 +38,7 @@
 <para>
 Modern ethernet subsystems are often separated into two pieces, the
 media access controller (sometimes known as a MAC) and the physical
-device or line interface (often refered to as a PHY).  In this case,
+device or line interface (often referred to as a PHY).  In this case,
 the MAC handles generating and parsing physical frames and the PHY
 handles how this data is actually moved to/from the wire.  The MAC 
 and PHY communicate via a special protocol, known as MII.  This MII
@@ -46,11 +46,11 @@ protocol can handle control over the PHY which allows for selection
 of such transmission criteria as line speed, duplex mode, etc.
 </para>
 <para>
-In most cases, etnernet drivers only need to bother with the PHY during
+In most cases, ethernet drivers only need to bother with the PHY during
 system initialization.  Since the details of the PHY are separate from
 the MAC, there are different drivers for each.  The drivers for the PHY
 are described by a set of exported functions which are commonly used by
-by the MAC.  The primary use of these functions currently is to initialize
+the MAC.  The primary use of these functions currently is to initialize
 the PHY and determine the status of the line connection.
 </para>
 <para>
@@ -96,7 +96,7 @@ struct _eth_phy_dev_entry {
 };
 
 </programlisting>
-The <varname>dev</varname> element points to the PHY speficic support
+The <varname>dev</varname> element points to the PHY specific support
 functions.  
 Currently, the only function which must be defined is <function>stat()</function>.
 </para>
@@ -147,7 +147,7 @@ The
 function may be called by a driver to cause the PHY device to
 be reset to a known state.
 Not all drivers will require this and this function may not even
-be possible, so it's use and behaviour is somewhat target specific.
+be possible, so it's use and behavior is somewhat target specific.
 </para>
 <para>
 Currently, the only function required of device specific drivers is
@@ -155,7 +155,7 @@ Currently, the only function required of device specific drivers is
 This routine should query appropriate registers in the PHY and return
 a status bitmap indicating the state of the physical connection.
 In the case where the PHY can auto-negotiate a line speed and condition,
-this information may be useful to the MAC to indicate what spped it should
+this information may be useful to the MAC to indicate what speed it should
 provide data, etc.
 The status bitmask contains these bits:
 <programlisting>