docs: clarify registry settings for sysadmins and ordering

Clarify that the new registry settings are aimed at enterprises and
system administrators, _and_ that the settings are at the lowest
precedence; they can always be overridden by the user.

Author: mjcheetham

docs/configuration.md

@@ -3,6 +3,7 @@
 [Git Credential Manager Core](usage.md) works out of the box for most users.
 
 Git Credential Manager Core (GCM Core) can be configured using Git's configuration files, and follows all of the same rules Git does when consuming the files.
+
 Global configuration settings override system configuration settings, and local configuration settings override global settings; and because the configuration details exist within Git's configuration files you can use Git's `git config` utility to set, unset, and alter the setting values. All of GCM Core's configuration settings begin with the term `credential`.
 
 GCM Core honors several levels of settings, in addition to the standard local \> global \> system tiering Git uses.

docs/enterprise-config.md

@@ -8,34 +8,45 @@ different mechanisms. In order of preference, those mechanisms are:
    1. Repository/local configuration (`.git/config`)
    2. User/global configuration (`$HOME/.gitconfig` or `%HOME%\.gitconfig`)
    3. Installation/system configuration (`etc/gitconfig`)
-3. Operating system specific configuration store
+3. Enterprise system administrator defaults
+4. Compiled default values
 
 This model largely matches what Git itself supports, namely environment
 variables that take precedence over Git configuration files.
 
-The addition of the operating system specific configuration store enables system
-administrators to configure defaults for many settings that may be required in
-an enterprise or corporate setting.
+The addition of the enterprise system administrator defaults enables those
+administrators to configure many GCM settings using familiar MDM tooling, rather
+than having to modify the Git installation configuration files.
 
----
+### User Freedom
 
-**Important:** We believe the user should _always_ be at liberty to configure
+We believe the user should _always_ be at liberty to configure
 Git and GCM exactly as they wish. By prefering environment variables and Git
-configuration files over OS store values, these only act as _default values_
+configuration files over system admin values, these only act as _default values_
 that can always be overriden by the user in the usual ways.
 
----
-
 ## Windows
 
 Default setting values come from the Windows Registry, specifically the
-`HKEY_LOCAL_MACHINE` hive under the following key:
+following keys:
+
+**32-bit Windows**
 
 ```text
-SOFTWARE\GitCredentialManager\Configuration
+HKEY_LOCAL_MACHINE\SOFTWARE\GitCredentialManager\Configuration
+```
+
+**64-bit Windows**
+
+```text
+HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\GitCredentialManager\Configuration
 ```
 
-By using the Windows Registry system administrators can use Group Policy to
+> GCM Core is a 32-bit executable on Windows. When running on a 64-bit
+installation of Windows registry access is transparently redirected to the
+`WOW6432Node` node.
+
+By using the Windows Registry, system administrators can use Group Policy to
 easily set defaults for GCM Core's settings.
 
 The names and possible values of all settings under this key are the same as
@@ -44,13 +55,6 @@ those of the [Git configuration](configuration.md) settings.
 The type of each registry key can be either `REG_SZ` (string) or `REG_DWORD`
 (integer).
 
-**Note:** GCM Core is a 32-bit executable on Windows. When running on a 64-bit
-installation of Windows registry access is transparently redirected to the
-`WOW6432Node`. This means the actual registry key on 64-bit Windows is:
-
-```text
-HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\GitCredentialManager\Configuration
-```
 
 ## macOS/Linux
 

docs/environment.md

@@ -2,7 +2,7 @@
 
 [Git Credential Manager Core](usage.md) works out of the box for most users. Configuration options are available to customize or tweak behavior.
 
-Git Credential Manager Core (GCM Core) can be configured using environment variables. **Environment variables take precedence over [configuration](configuration.md) options**. System administrators may also configure [default values](enterprise-config.md) for many settings used by GCM Core.
+Git Credential Manager Core (GCM Core) can be configured using environment variables. **Environment variables take precedence over [configuration](configuration.md) options and enterprise system administrator [default values](enterprise-config.md)**.
 
 For the complete list of environment variables GCM Core understands, see the list below.