diff options
author | John H Terpstra <jht@samba.org> | 2009-07-23 09:50:04 -0500 |
---|---|---|
committer | John H Terpstra <jht@samba.org> | 2009-07-23 09:50:04 -0500 |
commit | 9b18c5475e31507bb27e26e9f34142ead9dae349 (patch) | |
tree | b837a5235a0ca958b4b403c893eb5751a72b5fb6 /docs-xml/Samba3-HOWTO | |
parent | 94717ae8e5dfe2ccdb7f3557d5490708b00ae471 (diff) | |
download | samba-9b18c5475e31507bb27e26e9f34142ead9dae349.tar.gz samba-9b18c5475e31507bb27e26e9f34142ead9dae349.tar.bz2 samba-9b18c5475e31507bb27e26e9f34142ead9dae349.zip |
Fix typos reported by OPC Oota.
Diffstat (limited to 'docs-xml/Samba3-HOWTO')
-rw-r--r-- | docs-xml/Samba3-HOWTO/TOSHARG-WindowsClientConfig.xml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-WindowsClientConfig.xml b/docs-xml/Samba3-HOWTO/TOSHARG-WindowsClientConfig.xml index 50ee1c63e0..3facb2c35c 100644 --- a/docs-xml/Samba3-HOWTO/TOSHARG-WindowsClientConfig.xml +++ b/docs-xml/Samba3-HOWTO/TOSHARG-WindowsClientConfig.xml @@ -13,7 +13,7 @@ <para> <indexterm><primary>network difficulty</primary></indexterm> <indexterm><primary>network client</primary></indexterm> -<indexterm><primary>client client instructions</primary></indexterm> +<indexterm><primary>client instructions</primary></indexterm> Occasionally network administrators report difficulty getting Microsoft Windows clients to interoperate correctly with Samba servers. It seems that some folks just cannot accept the fact that the right way to configure an MS Windows network client is precisely as one would do when using MS Windows NT4 or 200x @@ -141,7 +141,7 @@ that are in common use today. These are: Many network administrators will want to use DHCP to configure all client TCP/IP protocol stack settings. (For information on how to configure the ISC DHCP server for Windows client support see <link linkend="DHCP">the DNS and DHCP Configuration Guide</link>, - <link linkend="DHCP">DHCP Server</link>. + <link linkend="DHCP">DHCP Server</link>). </para> <para> @@ -245,7 +245,7 @@ that are in common use today. These are: <indexterm><primary>protocol stack settings</primary></indexterm> Many network administrators will want to use DHCP to configure all client TCP/IP protocol stack settings. (For information on how to configure the ISC DHCP server - for Windows client support, see, <link linkend="DHCP"></link>. + for Windows client support, see, <link linkend="DHCP"></link>). </para> <para> @@ -339,7 +339,7 @@ that are in common use today. These are: Many network administrators will want to use DHCP to configure all client TCP/IP protocol stack settings. (For information on how to configure the ISC DHCP server for Windows client support see <link linkend="DHCP">the DNS and DHCP Configuration Guide</link>, - <link linkend="DHCP">DHCP Server</link>. The default setting on Windows Me workstations is for DHCP-enabled operation + <link linkend="DHCP">DHCP Server</link>). The default setting on Windows Me workstations is for DHCP-enabled operation (i.e., <guimenu>Obtain IP address automatically</guimenu> is enabled). See <link linkend="WME002"></link>. <figure id="WME002"><title>IP Address.</title><imagefile>WME002</imagefile></figure> </para> |