From: John H Terpstra Date: Fri, 25 Sep 2009 00:26:03 +0000 (-0500) Subject: Patches to fix typos thanks to OPC oota. X-Git-Url: http://git.samba.org/?a=commitdiff_plain;h=8a90106beb6344b94d159efd997d07d27a27f9b4;p=metze%2Fsamba%2Fwip.git Patches to fix typos thanks to OPC oota. --- diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-IDMAP.xml b/docs-xml/Samba3-HOWTO/TOSHARG-IDMAP.xml index 478199488160..f590334ebe67 100644 --- a/docs-xml/Samba3-HOWTO/TOSHARG-IDMAP.xml +++ b/docs-xml/Samba3-HOWTO/TOSHARG-IDMAP.xml @@ -36,7 +36,7 @@ This is followed by an overview of how the IDMAP facility may be implemented. The IDMAP facility is of concern where more than one Samba server (or Samba network client) is installed in a domain. Where there is a single Samba server, do not be too concerned regarding the IDMAP infrastructure &smbmdash; the default behavior of Samba is nearly always sufficient. -Where mulitple Samba servers are used it is often necessary to move data off one server and onto +Where multiple Samba servers are used it is often necessary to move data off one server and onto another, and that is where the fun begins! @@ -426,7 +426,7 @@ on Server Types and Security Modes. passdb backend BDC LDAP backend - Security identifiers used within a domain must be managed to avoid conflict and to preserve itegrity. + Security identifiers used within a domain must be managed to avoid conflict and to preserve integrity. In an NT4 domain context, the PDC manages the distribution of all security credentials to the backup domain controllers (BDCs). At this time the only passdb backend for a Samba domain controller that is suitable for such information is an LDAP backend. diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-TheNetCommand.xml b/docs-xml/Samba3-HOWTO/TOSHARG-TheNetCommand.xml index ea0ed485c00f..6e96ad1e1a3f 100644 --- a/docs-xml/Samba3-HOWTO/TOSHARG-TheNetCommand.xml +++ b/docs-xml/Samba3-HOWTO/TOSHARG-TheNetCommand.xml @@ -634,7 +634,7 @@ exit 0 Modify the &smb.conf; file so the NETLOGON stanza contains the parameters - shown in the Netlogon Example smb.conf file. + shown in the Netlogon Example smb.conf file as shown. @@ -1303,7 +1303,7 @@ Storing SID S-1-5-21-726309263-4128913605-1168186429 \ that the addition and deletion of shares using this tool depends on the availability of a suitable interface script. The interface scripts Sambas smbd uses are called , and - A set of example scripts are provided in the Samba source + . A set of example scripts are provided in the Samba source code tarball in the directory ~samba/examples/scripts. @@ -1630,7 +1630,7 @@ net rpc share MIGRATE ALL <share-name> -S <source> Printing needs vary greatly depending on the network environment and may be very simple or complex. If the need is very simple, the best solution to the implementation of printing support may well be to re-install everything from a clean slate instead of migrating older configurations. On the other hand, - a complex network that is integrated with many international offices and a multiplexity of local branch + a complex network that is integrated with many international offices and a complex arrangement of local branch offices, each of which form an inter-twined maze of printing possibilities, the ability to migrate all printer configurations is decidedly beneficial. To manually re-establish a complex printing network will take much time and frustration. Often it will not be possible to find driver files that are