Stage 1 of PHPTR Edits.

(This used to be commit 64a9e3e8619bf33dcf6b0ff8171b47a3e2581239)

1 files changed, 187 insertions, 189 deletions

diff --git a/docs/Samba3-HOWTO/TOSHARG-PDC.xml b/docs/Samba3-HOWTO/TOSHARG-PDC.xml
index e28de99470..7cd744767f 100644
--- a/docs/Samba3-HOWTO/TOSHARG-PDC.xml
+++ b/docs/Samba3-HOWTO/TOSHARG-PDC.xml
@@ -14,22 +14,22 @@
 <para>
 There are many who approach MS Windows networking with incredible misconceptions.
 That's okay, because it gives the rest of us plenty of opportunity to be of assistance.
-Those who really want help would be well advised to become familiar with information
+Those who really want help are well advised to become familiar with information
 that is already available.
 </para>
 
 <para>
-The reader is advised not to tackle this section without having first understood
+You are advised not to tackle this section without having first understood
 and mastered some basics. MS Windows networking is not particularly forgiving of
-mis-configuration. Users of MS Windows networking are likely to complain 
+misconfiguration. Users of MS Windows networking are likely to complain 
 of persistent niggles that may be caused by a broken network configuration.
-To a great many people, however, MS Windows networking starts with a Domain Controller
+To a great many people, however, MS Windows networking starts with a domain controller
 that in some magical way is expected to solve all network operational ills.
 </para>
 
 <para>
-<link linkend="domain-example">The diagram</link> shows a typical MS Windows Domain Security
-network environment. Workstations A, B and C are representative of many physical MS Windows
+<link linkend="domain-example">The Example Domain illustration</link> shows a typical MS Windows domain security
+network environment. Workstations A, B, and C are representative of many physical MS Windows
 network clients.
 </para>
 
@@ -38,10 +38,8 @@ network clients.
 	<imagefile scale="50">domain</imagefile>
 </figure>
 
-<?latex \newpage ?>
-
 <para>
-From the Samba mailing list one can readily identify many common networking issues.
+From the Samba mailing list we can readily identify many common networking issues.
 If you are not clear on the following subjects, then it will do much good to read the 
 sections of this HOWTO that deal with it. These are the most common causes of MS Windows
 networking problems:
@@ -69,7 +67,7 @@ organization.
 
 <para>
 Where is the right place to make mistakes? Only out of harms way. If you are going to
-make mistakes, then please do it on a test network, away from users and in such a way as
+make mistakes, then please do it on a test network, away from users, and in such a way as
 to not inflict pain on others. Do your learning on a test network.
 </para>
 
@@ -82,29 +80,29 @@ to not inflict pain on others. Do your learning on a test network.
 </para>
 
 <para>
-In a word, <emphasis>Single Sign On</emphasis>, or SSO for short. To many, this is the Holy
+In a word, <emphasis>single sign-on</emphasis>, or SSO for short. To many, this is the Holy
 Grail of MS Windows NT and beyond networking. SSO allows users in a well-designed network
 to log onto any workstation that is a member of the domain that their user account is in
 (or in a domain that has an appropriate trust relationship with the domain they are visiting)
-and they will be able to log onto the network and access resources (shares, files and printers)
-as if they are sitting at their home (personal) workstation. This is a feature of the Domain
-Security protocols.
+and they will be able to log onto the network and access resources (shares, files, and printers)
+as if they are sitting at their home (personal) workstation. This is a feature of the domain
+security protocols.
 </para>
 
 <para>
 <indexterm><primary>SID</primary></indexterm>
-The benefits of Domain Security are available to those sites that deploy a Samba PDC.
-A Domain provides a unique network security identifier (SID). Domain user and group security
+The benefits of domain security are available to those sites that deploy a Samba PDC.
+A domain provides a unique network security identifier (SID). Domain user and group security
 identifiers are comprised of the network SID plus a relative identifier (RID) that is unique to
-the account. User and Group SIDs (the network SID plus the RID) can be used to create Access Control
-Lists (ACLs) attached to network resources to provide organizational access control. UNIX systems
+the account. User and group SIDs (the network SID plus the RID) can be used to create access control
+lists (ACLs) attached to network resources to provide organizational access control. UNIX systems
 recognize only local security identifiers.
 </para>
 
 <note><para>
-Network clients of an MS Windows Domain Security Environment must be Domain Members to be
-able to gain access to the advanced features provided. Domain Membership involves more than just
-setting the workgroup name to the Domain name. It requires the creation of a Domain trust account
+Network clients of an MS Windows domain security environment must be domain members to be
+able to gain access to the advanced features provided. Domain membership involves more than just
+setting the workgroup name to the domain name. It requires the creation of a domain trust account
 for the workstation (called a machine account). Refer to <link linkend="domain-member">Domain Membership</link>
 for more information.
 </para></note>
@@ -129,12 +127,12 @@ The following functionalities are new to the Samba-3 release:
 	<listitem><para>
 	Introduces replaceable and multiple user account (authentication)
 	backends. In the case where the backend is placed in an LDAP database,
-	Samba-3 confers the benefits of a backend that can be distributed, replicated
+	Samba-3 confers the benefits of a backend that can be distributed and replicated
 	and is highly scalable.
 	</para></listitem>
 
 	<listitem><para>
-	Implements full Unicode support. This simplifies cross locale internationalization
+	Implements full Unicode support. This simplifies cross-locale internationalization
 	support. It also opens up the use of protocols that Samba-2.2.x had but could not use due
 	to the need to fully support Unicode.
 	</para></listitem>
@@ -147,17 +145,17 @@ The following functionalities are not provided by Samba-3:
 	<listitem><para>
 <indexterm><primary>SAM</primary></indexterm>
 <indexterm><primary>replication</primary></indexterm>
-	SAM replication with Windows NT4 Domain Controllers
-	(i.e., a Samba PDC and a Windows NT BDC or vice versa). This means Samba 
+	SAM replication with Windows NT4 domain controllers
+	(i.e., a Samba PDC and a Windows NT BDC, or vice versa). This means Samba 
 	cannot operate as a BDC when the PDC is Microsoft-based or 
 	replicate account data to Windows BDCs.
 	</para></listitem>
 	
 	<listitem><para>
-	Acting as a Windows 2000 Domain Controller (i.e., Kerberos and 
+	Acting as a Windows 2000 domain controller (i.e., Kerberos and 
 	Active Directory). In point of fact, Samba-3 does have some
-	Active Directory Domain Control ability that is at this time
-	purely experimental that is certain to change as it becomes a
+	Active Directory domain control ability that is at this time
+	purely experimental. That is certain to change as it becomes a
 	fully supported feature some time during the Samba-3 (or later)
 	life cycle. However, Active Directory is more then just SMB &smbmdash;
 	it's also LDAP, Kerberos, DHCP, and other protocols (with proprietary
@@ -165,34 +163,34 @@ The following functionalities are not provided by Samba-3:
 	</para></listitem>
 
 	<listitem><para>
-	The Windows 200x/XP MMC (Computer Management) Console can not be used
+	The Windows 200x/XP Microsoft Management Console (MMC) cannot be used
 	to manage a Samba-3 server. For this you can use only the MS Windows NT4
-	Domain Server manager and the MS Windows NT4 Domain User Manager. Both are
+	Domain Server Manager and the MS Windows NT4 Domain User Manager. Both are
 	part of the SVRTOOLS.EXE package mentioned later.
 	</para></listitem>
 </itemizedlist>
 
 <para>
 Windows 9x/Me/XP Home clients are not true members of a domain for reasons outlined
-in this chapter. The protocol for support of Windows 9x/Me style network (domain) logons
-is completely different from NT4/Windows 200x type domain logons and has been officially supported
-for some time. These clients use the old LanMan Network Logon facilities that are supported
+in this chapter. The protocol for support of Windows 9x/Me-style network (domain) logons
+is completely different from NT4/Windows 200x-type domain logons and has been officially supported
+for some time. These clients use the old LanMan network logon facilities that are supported
 in Samba since approximately the Samba-1.9.15 series.
 </para>
 
 <para>
 Samba-3 implements group mapping between Windows NT groups
 and UNIX groups (this is really quite complicated to explain in a short space). This is 
-discussed more fully in <link linkend="groupmapping">Group Mapping &smbmdash; MS Windows and UNIX</link>.
+discussed more fully in <link linkend="groupmapping">Group Mapping: MS Windows and UNIX</link>.
 </para>
 
 <para>
 <indexterm><primary>Machine Trust Accounts</primary></indexterm>
-Samba-3, like an MS Windows NT4 PDC or a Windows 200x Active Directory, needs to store
-user and Machine Trust Account information in a suitable backend data-store. 
-Refer to <link linkend="machine-trust-accounts">MS Windows Workstation/Server Machine Trust Accounts</link>. With Samba-3 there can be multiple
-backends for this. A complete discussion of account database backends can be found in
-<link linkend="passdb">Account Information Databases</link>.
+Samba-3, like an MS Windows NT4 PDC or a Windows 200x Active Directory, needs to store user and Machine Trust
+Account information in a suitable backend data-store.  Refer to <link linkend="machine-trust-accounts">MS
+Windows Workstation/Server Machine Trust Accounts</link>. With Samba-3 there can be multiple backends for
+this. A complete discussion of account database backends can be found in <link linkend="passdb">Account
+Information Databases</link>.
 </para>
 
 </sect1>
@@ -201,9 +199,9 @@ backends for this. A complete discussion of account database backends can be fou
 <title>Basics of Domain Control</title>
 
 <para>
-Over the years, public perceptions of what Domain Control really is has taken on an
-almost mystical nature. Before we branch into a brief overview of Domain Control,
-there are three basic types of Domain Controllers.
+Over the years, public perceptions of what domain control really is has taken on an
+almost mystical nature. Before we branch into a brief overview of domain control,
+there are three basic types of domain controllers.
 </para>
 
 <sect2>
@@ -216,34 +214,34 @@ there are three basic types of Domain Controllers.
 </itemizedlist>
 
 <para>
-The <emphasis>Primary Domain Controller</emphasis> or PDC plays an important role in MS 
-Windows NT4. In Windows 200x Domain Control architecture, this role is held by Domain Controllers.
-Folklore dictates that because of its role in the MS Windows
-network, the Domain Controller should be the most powerful and most capable machine in the network.
-As strange as it may seem to say this here, good overall network performance dictates that
-the entire infrastructure needs to be balanced. It is advisable to invest more in Stand-alone
-(Domain Member) servers than in the Domain Controllers.
+The <emphasis>Primary Domain Controller</emphasis> or PDC plays an important role in MS Windows NT4. In
+Windows 200x domain control architecture, this role is held by domain controllers.  Folklore dictates that
+because of its role in the MS Windows network, the domain controller should be the most powerful and most
+capable machine in the network.  As strange as it may seem to say this here, good overall network performance
+dictates that the entire infrastructure needs to be balanced. It is advisable to invest more in standalone
+(domain member) servers than in the domain controllers.
 </para>
 
 <para>
 <indexterm><primary>SAM</primary></indexterm>
-In the case of MS Windows NT4-style domains, it is the PDC that initiates a new Domain Control database.
+In the case of MS Windows NT4-style domains, it is the PDC that initiates a new domain control database.
 This forms a part of the Windows registry called the Security Account Manager (SAM). It plays a key
 part in NT4-type domain user authentication and in synchronization of the domain authentication
-database with Backup Domain Controllers. 
+database with BDCs. 
 </para>
 
 <para>
-With MS Windows 200x Server-based Active Directory domains, one Domain Controller initiates a potential
-hierarchy of Domain Controllers, each with their own area of delegated control. The master domain
-controller has the ability to override any downstream controller, but a down-line controller has
-control only over its down-line. With Samba-3, this functionality can be implemented using an
+With MS Windows 200x Server-based Active Directory domains, one domain controller initiates a potential
+hierarchy of domain controllers, each with its own area of delegated control. The master domain
+controller has the ability to override any downstream controller, but a downline controller has
+control only over its downline. With Samba-3, this functionality can be implemented using an
 LDAP-based user and machine account backend.
 </para>
 
 <para>
-New to Samba-3 is the ability to use a backend database that holds the same type of data as
-the NT4-style SAM database (one of the registry files)<footnote><para>See also <link linkend="passdb">Account Information Databases</link>.</para></footnote>.
+New to Samba-3 is the ability to use a backend database that holds the same type of data as the NT4-style SAM
+database (one of the registry files)<footnote><para>See also <link linkend="passdb">Account Information
+Databases</link>.</para>.</footnote>
 </para>
 
 <para>
@@ -253,51 +251,52 @@ On a network segment that has a BDC and a PDC, the BDC will most likely service
 logon requests. The PDC will answer network logon requests when the BDC is too busy (high load).
 A BDC can be promoted to a PDC. If the PDC is online at the time that a BDC is promoted to
 PDC, the previous PDC is automatically demoted to a BDC. With Samba-3, this is not an automatic
-operation; the PDC and BDC must be manually configured and changes also need to be made.
+operation; the PDC and BDC must be manually configured, and changes also need to be made.
 </para>
 
 <para>
 With MS Windows NT4, a decision is made at installation to determine what type of machine the server will be.
-It is possible to promote a BDC to a PDC and vice versa. The only way
-to convert a Domain Controller to a Domain Member server or a Stand-alone Server is to
-reinstall it. The install time choices offered are:
+It is possible to promote a BDC to a PDC, and vice versa. The only way to convert a domain controller to a
+domain member server or a standalone server is to reinstall it. The install time choices offered are:
 </para>
 
 <itemizedlist>
 	<listitem><para><emphasis>Primary Domain Controller</emphasis> &smbmdash; the one that seeds the domain SAM.</para></listitem>
 	<listitem><para><emphasis>Backup Domain Controller</emphasis> &smbmdash; one that obtains a copy of the domain SAM.</para></listitem>
-	<listitem><para><emphasis>Domain Member Server</emphasis> &smbmdash; one that has no copy of the domain SAM, rather it obtains authentication from a Domain Controller for all access controls.</para></listitem>
-	<listitem><para><emphasis>Stand-alone Server</emphasis> &smbmdash; one that plays no part is SAM synchronization, has its own authentication database and plays no role in Domain Security.</para></listitem>
+	<listitem><para><emphasis>Domain Member Server</emphasis> &smbmdash; one that has no copy of the domain SAM; rather
+		it obtains authentication from a domain controller for all access controls.</para></listitem>
+	<listitem><para><emphasis>Standalone Server</emphasis> &smbmdash; one that plays no part in SAM synchronization,
+		has its own authentication database, and plays no role in domain security.</para></listitem>
 </itemizedlist>
 
 <para>
-With MS Windows 2000, the configuration of Domain Control is done after the server has been
+With MS Windows 2000, the configuration of domain control is done after the server has been
 installed. Samba-3 is capable of acting fully as a native member of a Windows 200x server
 Active Directory domain.
 </para>
 
 <para>
 <indexterm><primary>replication</primary><secondary>SAM</secondary></indexterm>
-New to Samba-3 is the ability to function fully as an MS Windows NT4-style Domain Controller,
+New to Samba-3 is the ability to function fully as an MS Windows NT4-style domain controller,
 excluding the SAM replication components. However, please be aware that Samba-3 also supports the
-MS Windows 200x Domain Control protocols.
+MS Windows 200x domain control protocols.
 </para>
 
 <para>
-At this time any appearance that Samba-3 is capable of acting as an
-<emphasis>Domain Controller</emphasis> in native ADS mode is limited and experimental in nature.
+At this time any appearance that Samba-3 is capable of acting as a
+<emphasis>domain controller</emphasis> in native ADS mode is limited and experimental in nature.
 This functionality should not be used until the Samba Team offers formal support for it.
 At such a time, the documentation will be revised to duly reflect all configuration and
-management requirements. Samba can act as a NT4-style DC in a Windows 2000/XP 
+management requirements. Samba can act as a NT4-style domain controller in a Windows 2000/XP 
 environment. However, there are certain compromises:
 
 <itemizedlist>
 	<listitem><para>No machine policy files.</para></listitem>
 	<listitem><para>No Group Policy Objects.</para></listitem>
-	<listitem><para>No synchronously executed AD logon scripts.</para></listitem>
+	<listitem><para>No synchronously executed Active Directory logon scripts.</para></listitem>
 	<listitem><para>Can't use Active Directory management tools to manage users and machines.</para></listitem>
-	<listitem><para>Registry changes tattoo the main registry, while with AD they do not leave permanent changes in effect.</para></listitem>
-	<listitem><para>Without AD you cannot perform the function of exporting specific applications to specific users or groups.</para></listitem>
+	<listitem><para>Registry changes tattoo the main registry, while with Active Directory they do not leave permanent changes in effect.</para></listitem>
+	<listitem><para>Without Active Directory you cannot perform the function of exporting specific applications to specific users or groups.</para></listitem>
 </itemizedlist>
 </para>
 
@@ -307,36 +306,36 @@ environment. However, there are certain compromises:
 <title>Preparing for Domain Control</title>
 
 <para>
-There are two ways that MS Windows machines may interact with each other, with other servers
-and with Domain Controllers: either as <emphasis>Stand-alone</emphasis> systems, more commonly
-called <emphasis>Workgroup</emphasis> members, or as full participants in a security system,
-more commonly called <emphasis>Domain</emphasis> members.
+There are two ways that MS Windows machines may interact with each other, with other servers,
+and with domain controllers: either as <emphasis>standalone</emphasis> systems, more commonly
+called <emphasis>workgroup</emphasis> members, or as full participants in a security system,
+more commonly called <emphasis>domain</emphasis> members.
 </para>
 
 <para>
-It should be noted that <emphasis>Workgroup</emphasis> membership involves no special configuration
+It should be noted that workgroup membership involves no special configuration
 other than the machine being configured so the network configuration has a commonly used name
 for its workgroup entry. It is not uncommon for the name WORKGROUP to be used for this. With this
-mode of configuration, there are no Machine Trust Accounts and any concept of membership as such
+mode of configuration, there are no Machine Trust Accounts, and any concept of membership as such
 is limited to the fact that all machines appear in the network neighborhood to be logically
 grouped together. Again, just to be clear: <emphasis>workgroup mode does not involve security machine 
 accounts</emphasis>.
 </para>
 
 <para>
-Domain Member machines have a machine account in the Domain accounts database. A special procedure
-must be followed on each machine to effect Domain Membership. This procedure, which can be done
-only by the local machine Administrator account, will create the Domain machine account (if it does
+Domain member machines have a machine account in the domain accounts database. A special procedure
+must be followed on each machine to effect domain membership. This procedure, which can be done
+only by the local machine Administrator account, creates the domain machine account (if it does
 not exist), and then initializes that account. When the client first logs onto the
-Domain it triggers a machine password change.
+domain, it triggers a machine password change.
 </para>
 
 <note><para>
-When Samba is configured as a Domain Controller, secure network operation demands that
-all MS Windows NT4/200x/XP Professional clients should be configured as Domain Members.
-If a machine is not made a member of the Domain, then it will operate like a workgroup
-(Stand-alone) machine. Please refer to <link linkend="domain-member">Domain Membership</link> chapter for
-information regarding Domain Membership.
+When Samba is configured as a domain controller, secure network operation demands that
+all MS Windows NT4/200x/XP Professional clients should be configured as domain members.
+If a machine is not made a member of the domain, then it will operate like a workgroup
+(standalone) machine. Please refer to <link linkend="domain-member">Domain Membership</link>, for
+information regarding domain membership.
 </para></note>
 
 <para>
@@ -346,14 +345,14 @@ NT4/200x/XP clients:
 
 <itemizedlist>
 	<listitem><para>Configuration of basic TCP/IP and MS Windows networking.</para></listitem>
-	<listitem><para>Correct designation of the Server Role (<smbconfoption name="security">user</smbconfoption>).</para></listitem>
-	<listitem><para>Consistent configuration of Name Resolution<footnote><para>See <link linkend="NetworkBrowsing">Network Browsing</link>, and 
-		<link linkend="integrate-ms-networks">Integrating MS Windows Networks with Samba</link>.</para></footnote>.</para></listitem>
+	<listitem><para>Correct designation of the server role (<smbconfoption name="security">user</smbconfoption>).</para></listitem>
+	<listitem><para>Consistent configuration of name resolution.<footnote><para>See <link linkend="NetworkBrowsing">Network Browsing</link>, and 
+		<link linkend="integrate-ms-networks">Integrating MS Windows Networks with Samba</link>.</para></footnote></para></listitem>
 	<listitem><para>Domain logons for Windows NT4/200x/XP Professional clients.</para></listitem>
-	<listitem><para>Configuration of Roaming Profiles or explicit configuration to force local profile usage.</para></listitem>
+	<listitem><para>Configuration of roaming profiles or explicit configuration to force local profile usage.</para></listitem>
 	<listitem><para>Configuration of network/system policies.</para></listitem>
 	<listitem><para>Adding and managing domain user accounts.</para></listitem>
-	<listitem><para>Configuring MS Windows client machines to become Domain Members.</para></listitem>
+	<listitem><para>Configuring MS Windows client machines to become domain members.</para></listitem>
 </itemizedlist>
 
 <para>
@@ -363,38 +362,38 @@ The following provisions are required to serve MS Windows 9x/Me clients:
 <itemizedlist>
 	<listitem><para>Configuration of basic TCP/IP and MS Windows networking.</para></listitem>
 	<listitem><para>Correct designation of the server role (<smbconfoption name="security">user</smbconfoption>).</para></listitem>
-	<listitem><para>Network Logon Configuration (since Windows 9x/Me/XP Home are not technically domain
+	<listitem><para>Network logon configuration (since Windows 9x/Me/XP Home are not technically domain
 	members, they do not really participate in  the security aspects of Domain logons as such).</para></listitem>
-	<listitem><para>Roaming Profile Configuration.</para></listitem>
-	<listitem><para>Configuration of System Policy handling.</para></listitem>
+	<listitem><para>Roaming profile configuration.</para></listitem>
+	<listitem><para>Configuration of system policy handling.</para></listitem>
 	<listitem><para>Installation of the network driver <quote>Client for MS Windows Networks</quote> and configuration
 	to log onto the domain.</para></listitem>
-	<listitem><para>Placing Windows 9x/Me clients in User Level Security &smbmdash; if it is desired to allow
-	all client share access to be controlled according to domain user/group identities.</para></listitem>
+	<listitem><para>Placing Windows 9x/Me clients in user-level security &smbmdash; if it is desired to allow
+	all client-share access to be controlled according to domain user/group identities.</para></listitem>
 	<listitem><para>Adding and managing domain user accounts.</para></listitem>
 </itemizedlist>
 
 <note><para>
-Roaming Profiles and System/Network policies are advanced network administration topics
-that are covered in the <link linkend="ProfileMgmt">Desktop Profile Management</link> and 
-<link linkend="PolicyMgmt">System and Account Policies</link> chapters of this document. However, these are not
+Roaming profiles and system/network policies are advanced network administration topics
+that are covered in <link linkend="ProfileMgmt">Desktop Profile Management</link> and
+<link linkend="PolicyMgmt">System and Account Policies</link> of this document. However, these are not
 necessarily specific to a Samba PDC as much as they are related to Windows NT networking concepts.
 </para></note>
 
 <para>
-A Domain Controller is an SMB/CIFS server that:
+A domain controller is an SMB/CIFS server that:
 </para>
 
 <itemizedlist>
 	<listitem><para>
-	Registers and advertises itself as a Domain Controller (through NetBIOS broadcasts
+	Registers and advertises itself as a domain controller (through NetBIOS broadcasts
 	as well as by way of name registrations either by Mailslot Broadcasts over UDP broadcast,
-	to a WINS server over UDP uni-cast, or via DNS and Active Directory).
+	to a WINS server over UDP unicast, or via DNS and Active Directory).
 	</para></listitem>
 
 	<listitem><para>
 	Provides the NETLOGON service. (This is actually a collection of services that runs over
-	multiple protocols. These include the LanMan Logon service, the Netlogon service,
+	multiple protocols. These include the LanMan logon service, the Netlogon service,
 	the Local Security Account service, and variations of them.)
 	</para></listitem>
 
@@ -404,26 +403,27 @@ A Domain Controller is an SMB/CIFS server that:
 </itemizedlist>
 
 <para>
-It is rather easy to configure Samba to provide these. Each Samba Domain Controller must provide
-the NETLOGON service that Samba calls the <smbconfoption name="domain logons"/> functionality
-(after the name of the parameter in the &smb.conf; file). Additionally, one server in a Samba-3
-Domain must advertise itself as the Domain Master Browser<footnote><para>See <link linkend="NetworkBrowsing">Network Browsing</link>.</para></footnote>.
-This causes the Primary Domain Controller to claim a domain-specific NetBIOS name that identifies it as a
-Domain Master Browser for its given domain or workgroup. Local master browsers in the same domain or workgroup on
-broadcast-isolated subnets then ask for a complete copy of the browse list for the whole wide area network.
-Browser clients will then contact their Local Master Browser, and will receive the domain-wide browse list,
-instead of just the list for their broadcast-isolated subnet.
+It is rather easy to configure Samba to provide these. Each Samba domain controller must provide the NETLOGON
+service that Samba calls the <smbconfoption name="domain logons"/> functionality (after the name of the
+parameter in the &smb.conf; file). Additionally, one server in a Samba-3 domain must advertise itself as the
+domain master browser.<footnote><para>See <link linkend="NetworkBrowsing">Network
+Browsing</link>.</para></footnote> This causes the PDC to claim a domain-specific NetBIOS name that identifies
+it as a DMB for its given domain or workgroup. Local master browsers (LMBs) in the same domain or workgroup on
+broadcast-isolated subnets then ask for a complete copy of the browse list for the whole wide-area network.
+Browser clients then contact their LMB, and will receive the domain-wide browse list instead of just the list
+for their broadcast-isolated subnet.
 </para>
 
 </sect2>
 </sect1>
 
 <sect1>
-<title>Domain Control &smbmdash; Example Configuration</title>
+<title>Domain Control: Example Configuration</title>
 
 <para>
 The first step in creating a working Samba PDC is to understand the parameters necessary
-in &smb.conf;. An example &smb.conf; for acting as a PDC can be found in <link linkend="pdc-example">the next example</link>. 
+in &smb.conf;. An example &smb.conf; for acting as a PDC can be found in <link linkend="pdc-example">the
+smb.conf for being a PDC</link>. 
 </para>
 
 <example id="pdc-example">
@@ -469,7 +469,7 @@ The basic options shown in <link linkend="pdc-example">this example</link> are e
 		default accounts and is included by default, there is no need to add it explicitly.</para>
 
 		<para>
-		Where use of backup Domain Controllers (BDCs) is intended, the only logical choice is
+		Where use of BDCs is intended, the only logical choice is
 		to use LDAP so the passdb backend can be distributed. The tdbsam and smbpasswd files
 		cannot effectively be distributed and therefore should not be used.
 		</para></listitem>
@@ -477,12 +477,12 @@ The basic options shown in <link linkend="pdc-example">this example</link> are e
 	<varlistentry><term>Domain Control Parameters </term>
 		<listitem><para>
 		The parameters <emphasis>os level, preferred master, domain master, security, 
-		encrypt passwords, and domain logons</emphasis> play a central role in assuring domain
+		encrypt passwords</emphasis>, and <emphasis>domain logons</emphasis> play a central role in assuring domain
 		control and network logon support.</para>
 
 		<para>
-		The <emphasis>os level</emphasis> must be set at or above a value of 32. A Domain Controller
-		must be the Domain Master Browser, must be set in <emphasis>user</emphasis> mode security,
+		The <emphasis>os level</emphasis> must be set at or above a value of 32. A domain controller
+		must be the DMB, must be set in <emphasis>user</emphasis> mode security,
 		must support Microsoft-compatible encrypted passwords, and must provide the network logon
 		service (domain logons). Encrypted passwords must be enabled. For more details on how 
 		to do this, refer to <link linkend="passdb">Account Information Databases</link>.
@@ -490,7 +490,7 @@ The basic options shown in <link linkend="pdc-example">this example</link> are e
 	</varlistentry>
 	<varlistentry><term>Environment Parameters </term>
 		<listitem><para>
-		The parameters <emphasis>logon path, logon home, logon drive, and logon script</emphasis> are
+		The parameters <emphasis>logon path, logon home, logon drive</emphasis>, and <emphasis>logon script</emphasis> are
 		environment support settings that help to facilitate client logon operations and that help
 		to provide automated control facilities to ease network management overheads. Please refer
 		to the man page information for these parameters.
@@ -498,10 +498,10 @@ The basic options shown in <link linkend="pdc-example">this example</link> are e
 	</varlistentry>
 	<varlistentry><term>NETLOGON Share </term>
 		<listitem><para>
-		The NETLOGON share plays a central role in domain logon and Domain Membership support.
-		This share is provided on all Microsoft Domain Controllers. It is used to provide logon
-		scripts, to store Group Policy files (NTConfig.POL), as well as to locate other common
-		tools that may be needed for logon processing. This is an essential share on a Domain Controller.
+		The NETLOGON share plays a central role in domain logon and domain membership support.
+		This share is provided on all Microsoft domain controllers. It is used to provide logon
+		scripts, to store group policy files (NTConfig.POL), as well as to locate other common
+		tools that may be needed for logon processing. This is an essential share on a domain controller.
 		</para></listitem>
 	</varlistentry>
 	<varlistentry><term>PROFILE Share </term>
@@ -531,7 +531,7 @@ of operation. The following &smb.conf; parameters are the essentials alone:
 </para>
 
 <para>
-The additional parameters shown in the longer listing above just makes for
+The additional parameters shown in the longer listing in this section just make for
 a more complete explanation.
 </para></note>
 
@@ -541,21 +541,21 @@ a more complete explanation.
 <title>Samba ADS Domain Control</title>
 
 <para>
-Samba-3 is not, and cannot act as, an Active Directory Server. It cannot truly function as
-an Active Directory Primary Domain Controller. The protocols for some of the functionality
-of Active Directory Domain Controllers has been partially implemented on an experimental
+Samba-3 is not, and cannot act as, an Active Directory server. It cannot truly function as
+an Active Directory PDC. The protocols for some of the functionality
+of Active Directory domain controllers has been partially implemented on an experimental
 only basis. Please do not expect Samba-3 to support these protocols. Do not depend
 on any such functionality either now or in the future. The Samba Team may remove these
 experimental features or may change their behavior. This is mentioned for the benefit of those
 who have discovered secret capabilities in Samba-3 and who have asked when this functionality will be
-completed. The answer is maybe or maybe never!
+completed. The answer is maybe someday or maybe never!
 </para>
 
 <para>
 To be sure, Samba-3 is designed to provide most of the functionality that Microsoft Windows NT4-style
-Domain Controllers have. Samba-3 does not have all the capabilities of Windows NT4, but it does have
+domain controllers have. Samba-3 does not have all the capabilities of Windows NT4, but it does have
 a number of features that Windows NT4 domain controllers do not have. In short, Samba-3 is not NT4 and it
-is not Windows Server 200x, it is not an Active Directory server. We hope this is plain and simple
+is not Windows Server 200x: it is not an Active Directory server. We hope this is plain and simple
 enough for all to understand.
 </para>
 
@@ -565,17 +565,17 @@ enough for all to understand.
 <title>Domain and Network Logon Configuration</title>
 
 <para>
-The subject of Network or Domain Logons is discussed here because it forms
-an integral part of the essential functionality that is provided by a Domain Controller.
+The subject of network or domain logons is discussed here because it forms
+an integral part of the essential functionality that is provided by a domain controller.
 </para>
 
 <sect2>
 <title>Domain Network Logon Service</title>
 
 <para>
-All Domain Controllers must run the netlogon service (<emphasis>domain logons</emphasis>
-in Samba). One Domain Controller must be configured with <smbconfoption name="domain master">Yes</smbconfoption>
-(the Primary Domain Controller); on all Backup Domain Controllers <smbconfoption name="domain master">No</smbconfoption>
+All domain controllers must run the netlogon service (<emphasis>domain logons</emphasis>
+in Samba). One domain controller must be configured with <smbconfoption name="domain master">Yes</smbconfoption>
+(the PDC); on all BDCs <smbconfoption name="domain master">No</smbconfoption>
 must be set.
 </para>
 
@@ -603,14 +603,14 @@ must be set.
 
 <para>
 To be completely clear: If you want MS Windows XP Home Edition to integrate with your
-MS Windows NT4 or Active Directory Domain Security, understand it cannot be done.
+MS Windows NT4 or Active Directory domain security, understand it cannot be done.
 The only option is to purchase the upgrade from MS Windows XP Home Edition to
 MS Windows XP Professional.
 </para>
 
 <note><para>
-MS Windows XP Home Edition does not have the ability to join any type of Domain
-Security facility. Unlike MS Windows 9x/Me, MS Windows XP Home Edition also completely
+MS Windows XP Home Edition does not have the ability to join any type of domain
+security facility. Unlike MS Windows 9x/Me, MS Windows XP Home Edition also completely
 lacks the ability to log onto a network.
 </para></note>
 
@@ -645,26 +645,26 @@ It should be noted that browsing is totally orthogonal to logon support.
 
 <para>
 Issues related to the single-logon network model are discussed in this
-section. Samba supports domain logons, network logon scripts and user
-profiles for MS Windows for workgroups and MS Windows 9X/ME clients,
+section. Samba supports domain logons, network logon scripts, and user
+profiles for MS Windows for Workgroups and MS Windows 9x/Me clients,
 which are the focus of this section.
 </para>
 
 <para>
-When an SMB client in a domain wishes to logon, it broadcasts requests for a
-logon server. The first one to reply gets the job, and validates its
+When an SMB client in a domain wishes to log on, it broadcasts requests for a
+logon server. The first one to reply gets the job and validates its
 password using whatever mechanism the Samba administrator has installed.
-It is possible (but ill advised ) to create a domain where the user
-database is not shared between servers, i.e., they are effectively workgroup
+It is possible (but ill advised) to create a domain where the user
+database is not shared between servers; that is, they are effectively workgroup
 servers advertising themselves as participating in a domain. This
 demonstrates how authentication is quite different from but closely
 involved with domains.
 </para>
 
 <para>
-Using these features you can make your clients verify their logon via
-the Samba server; make clients run a batch file when they logon to
-the network and download their preferences, desktop and start menu.
+Using these features, you can make your clients verify their logon via
+the Samba server, make clients run a batch file when they log on to
+the network and download their preferences, desktop, and start menu.
 </para>
 
 <para><emphasis>
@@ -745,7 +745,7 @@ The main difference between a PDC and a Windows 9x/Me logon server configuration
 <itemizedlist>
 <listitem><para>
 	Password encryption is not required for a Windows 9x/Me logon server. But note
-	that beginning with MS Windows 98 the default setting is that plain-text
+	that beginning with MS Windows 98 the default setting is that plaintext
 	password support is disabled. It can be re-enabled with the registry
 	changes that are documented in <link linkend="PolicyMgmt">System and Account Policies</link>.
 	</para></listitem>
@@ -761,7 +761,7 @@ network logon services that MS Windows 9x/Me expect to find.
 </para>
 
 <note><para>
-Use of plain-text passwords is strongly discouraged. Where used they are easily detected
+Use of plaintext passwords is strongly discouraged. Where used they are easily detected
 using a sniffer tool to examine network traffic.
 </para></note>
 
@@ -773,39 +773,37 @@ using a sniffer tool to examine network traffic.
 
 <para>
 There are a few comments to make in order to tie up some loose ends. There has been
-much debate over the issue of whether it is okay to configure Samba as a Domain
-Controller in security modes other than user. The only security mode that will
+much debate over the issue of whether it is okay to configure Samba as a domain
+controller in security modes other than user. The only security mode that will
 not work due to technical reasons is share-mode security. Domain and server mode
-security are really just a variation on SMB User Level Security.
+security are really just a variation on SMB user-level security.
 </para>
 
 <para>
-Actually, this issue is also closely tied to the debate on whether 
-Samba must be the Domain Master Browser for its workgroup
-when operating as a DC. While it may technically be possible
-to configure a server as such (after all, browsing and domain logons
-are two distinctly different functions), it is not a good idea to do
-so. You should remember that the DC must register the DOMAIN&lt;#1b&gt; NetBIOS 
-name. This is the name used by Windows clients to locate the DC.
-Windows clients do not distinguish between the DC and the DMB.
-A DMB is a Domain Master Browser &smbmdash; see <link linkend="DMB">Configuring WORKGROUP Browsing</link> section.
-For this reason, it is wise to configure the Samba DC as the DMB.
+Actually, this issue is also closely tied to the debate on whether Samba must be the DMB for its workgroup
+when operating as a domain controller. While it may technically be possible to configure a server as such
+(after all, browsing and domain logons are two distinctly different functions), it is not a good idea to do
+so. You should remember that the domain controller must register the DOMAIN&lt;#1b&gt; NetBIOS name. This is
+the name used by Windows clients to locate the domain controller.  Windows clients do not distinguish between
+the domain controller and the DMB.  A DMB is a Domain Master Browser &smbmdash; see <link
+linkend="NetworkBrowsing">The Network Browsing Chapter</link>, <link linkend="DMB">Configuring WORKGROUP
+Browsing</link> section.  For this reason, it is wise to configure the Samba domain controller as the DMB.
 </para>
 
 <para>
-Now back to the issue of configuring a Samba DC to use a mode other than
+Now back to the issue of configuring a Samba domain controller to use a mode other than
 <smbconfoption name="security">user</smbconfoption>. If a Samba host is
-configured to use another SMB server or DC in order to validate user connection requests,
+configured to use another SMB server or domain controller in order to validate user connection requests,
 it is a fact that some other machine on the network (the <smbconfoption name="password server"/>)
-knows more about the user than the Samba host. About 99% of the time, this other host is
-a Domain Controller. Now to operate in domain mode security, the <smbconfoption name="workgroup"/>
-parameter must be set to the name of the Windows NT domain (which already has a Domain Controller).
-If the domain does not already have a Domain Controller, you do not yet have a Domain.
+knows more about the user than the Samba host. About 99 percent of the time, this other host is
+a domain controller. Now to operate in domain mode security, the <smbconfoption name="workgroup"/>
+parameter must be set to the name of the Windows NT domain (which already has a domain controller).
+If the domain does not already have a domain controller, you do not yet have a domain.
 </para>
 
 <para>
-Configuring a Samba box as a DC for a domain that already by definition has a
-PDC is asking for trouble. Therefore, you should always configure the Samba DC
+Configuring a Samba box as a domain controller for a domain that already by definition has a
+PDC is asking for trouble. Therefore, you should always configure the Samba domain controller
 to be the DMB for its domain and set <smbconfoption name="security">user</smbconfoption>.
 This is the only officially supported mode of operation.
 </para>
@@ -858,9 +856,9 @@ will remove all network drive connections:
 
 <para>
 Further, if the machine is already a <quote>member of a workgroup</quote> that 
-is the same name as the domain you are joining (bad idea) you will 
-get this message. Change the workgroup name to something else, it 
-does not matter what, reboot, and try again.
+is the same name as the domain you are joining (bad idea), you will 
+get this message. Change the workgroup name to something else &smbmdash; it 
+does not matter what &smbmdash; reboot, and try again.
 </para>
 </sect2>
 
@@ -869,7 +867,7 @@ does not matter what, reboot, and try again.
 
 <para><quote>I joined the domain successfully but after upgrading 
 to a newer version of the Samba code I get the message, <errorname>`The system 
-cannot log you on (C000019B), Please try again or consult your 
+cannot log you on (C000019B). Please try again or consult your 
 system administrator</errorname> when attempting to logon.'</quote>
 </para>
 
@@ -893,9 +891,9 @@ To reset or change the domain SID you can use the net command as follows:
 </para>
 
 <para>
-Workstation Machine Trust Accounts work only with the Domain (or network) SID. If this SID changes
-Domain Members (workstations) will not be able to log onto the domain. The original Domain SID
-can be recovered from the secrets.tdb file. The alternative is to visit each workstation to re-join
+Workstation Machine Trust Accounts work only with the domain (or network) SID. If this SID changes,
+domain members (workstations) will not be able to log onto the domain. The original domain SID
+can be recovered from the secrets.tdb file. The alternative is to visit each workstation to rejoin
 it to the domain.
 </para>
 
@@ -905,20 +903,20 @@ it to the domain.
 <title>The Machine Trust Account Is Not Accessible</title>
 
 <para>
-<quote>When I try to join the domain I get the message, <errorname>`The machine account 
-for this computer either does not exist or is not accessible'</errorname>. What's 
+<quote>When I try to join the domain I get the message, <errorname>"The machine account 
+for this computer either does not exist or is not accessible</errorname>." What's 
 wrong?</quote>
 </para>
 
 <para>
 This problem is caused by the PDC not having a suitable Machine Trust Account. 
 If you are using the <smbconfoption name="add machine script"/> method to create 
-accounts then this would indicate that it has not worked. Ensure the domain 
+accounts, then this would indicate that it has not worked. Ensure the domain 
 admin user system is working.
 </para>
 
 <para>
-Alternately, if you are creating account entries manually then they 
+Alternately, if you are creating account entries manually, then they 
 have not been created correctly. Make sure that you have the entry 
 correct for the Machine Trust Account in <filename>smbpasswd</filename> file on the Samba PDC. 
 If you added the account using an editor rather than using the smbpasswd 
@@ -936,7 +934,7 @@ client can cause this problem.  Make sure that these are consistent for both cli
 <sect2>
 <title>Account Disabled</title>
 
-<para><quote>When I attempt to login to a Samba Domain from a NT4/W200x workstation,
+<para><quote>When I attempt to log in to a Samba domain from a NT4/W200x workstation,
 I get a message about my account being disabled.</quote></para>
 
 <para>
@@ -952,7 +950,7 @@ Enable the user accounts with <userinput>smbpasswd -e <replaceable>username</rep
 <para><quote>Until a few minutes after Samba has started, clients get the error `Domain Controller Unavailable'</quote></para>
 
 <para>
-A Domain Controller has to announce its role on the network. This usually takes a while. Be patient for up to fifteen minutes,
+A domain controller has to announce its role on the network. This usually takes a while. Be patient for up to 15 minutes,
 then try again.
 </para>
 </sect2>
@@ -964,21 +962,21 @@ then try again.
 <indexterm><primary>schannel</primary></indexterm>
 <indexterm><primary>signing</primary></indexterm>
 After successfully joining the domain, user logons fail with one of two messages: one to the
-effect that the Domain Controller cannot be found; the other claims that the account does not
+effect that the domain controller cannot be found; the other claims that the account does not
 exist in the domain or that the password is incorrect. This may be due to incompatible
 settings between the Windows client and the Samba-3 server for <emphasis>schannel</emphasis>
 (secure channel) settings or <emphasis>smb signing</emphasis> settings. Check your Samba
-settings for <emphasis> client schannel, server schannel, client signing, server signing</emphasis>
-by executing:
+settings for <emphasis>client schannel</emphasis>, <emphasis>server schannel</emphasis>,
+<emphasis>client signing</emphasis>, <emphasis>server signing</emphasis> by executing:
 <screen>
 <command>testparm -v | more</command> and looking for the value of these parameters.
 </screen>
 </para>
 
 <para>
-Also use the Microsoft Management Console &smbmdash; Local Security Settings. This tool is available from the
+Also use the MMC &smbmdash; Local Security Settings. This tool is available from the
 Control Panel. The Policy settings are found in the Local Policies/Security Options area and are prefixed by
-<emphasis>Secure Channel: ..., and Digitally sign ....</emphasis>.
+<emphasis>Secure Channel:..., and Digitally sign...</emphasis>.
 </para>
 
 <para>