samba-functionality/overview.md

@@ -16,7 +16,7 @@ operates as:
 * File server, as well as providing printing services.
 * Active Directory (AD) Domain Controller (DC)
 
-## Network server
+## File server
 
 Samba is best known as a [File Server](https://www.samba.org/samba/docs/current/man-html/smbd.8.html),
 sharing POSIX file systems to Microsoft's
@@ -117,7 +117,7 @@ so the *machine account* (the object in the domain that represents the
 domain member) can be used to make or accept Kerberised network
 requests.
 
-## Client
+## Client utilities
 
 Samba provides a wide range of client utilities.
 These are documented in more detail in Appendix I.
@@ -135,28 +135,20 @@ are `samba-tool domain provision` used to create a new AD Domain,
 `samba-tool` is based on a set of Python APIs in the Samba [codebase](https://git.samba.org/?p=samba.git;a=tree;f=python).
 These set of python APIs could potentially be re-used to build custom tools.
 
-## [*Classic* or NT4-like Domain Controller](https://wiki.samba.org/index.php/Setting_up_Samba_as_an_NT4_PDC_(Quick_Start))
+## Legacy NT4-like Domain Controller
 
-Samba provides a domain controller using technologies similar to NT4.
-This can be backed on to an external LDAP server such as OpenLDAP and
-so was very popular for being able to scale very well and leverage
+Samba can provide a [_Classic_ Domain Controller](https://wiki.samba.org/index.php/Setting_up_Samba_as_an_NT4_PDC_(Quick_Start)) using technologies similar to NT4.
+Prior to supporting AD DC (i.e. on Samba 3 releases), the solution was to back Samba on to an external LDAP server such as OpenLDAP.
+This solution was very popular for being able to emulate an NT4 domain, scale very well, and leverage
 OpenLDAP for multi-master replication.
-
-* [source3/rpc_server](https://git.samba.org/?p=samba.git;a=tree;f=source3/rpc_server)
-
-### Naming
-
-The name Samba classic domain never caught on, and some people also
-talk about these as Samba 3 domains, because Samba 3.x did not contain
-the AD DC but could emulate an NT4 domain (and did so very well).
-
-The Samba Team avoids the name *Samba 3 domain* because that
-functionality still exists in Samba 4.x and users of Samba 3.x are
-strongly encouraged to upgrade.
+This solution is still supported on Samba 4 releases, although it's recommended to run Samba as an AD DC instead.
 
 This domain is also not entirely NT4-like because Windows clients will
 use modern cryptography against such a Samba domain that NT4 never
 supported.
 
+Sometimes this solution is referred to as a *Samba 3 domain*, although that name is not entirely correct.
+Samba tried to refer to this as a _Classic Domain_, however that name never really caught on.
+