anchor.diff:  
   This section contains examples for the link:#sync-ldap-rfc-2307[RFC 2307],
   link:#sync-ldap-active-directory[Active Directory], and
  -link:#sync-ldap-augmented-active-directory[Augmented Active Directory] schemas.
  +link:#sync-ldap-augmented-active-directory[augmented Active Directory] schemas.
   All of the following examples synchronize a group named *admins* that has two
   members: *Jane* and *Jim*. Each example explains:
   
   * How the group and users are added to the LDAP server.
   * What the LDAP sync configuration file looks like.
  -* What the resulting group record in OpenShift will be after synchronization.
  +* What the resulting Group record in OpenShift will be after synchronization.
   
   [[sync-ldap-rfc-2307]]
   === RFC 2307
  
positive.code: LDAP (`ldaps://`) URLs connect using TLS, and insecure LDAP (`ldap://`) URLs are
  upgraded to TLS.
  <3> The attribute that uniquely identifies a group on the LDAP server.
  <4> The attribute to use as the name of the group.
  <5> The attribute on the group that stores the membership information.
  <6> The attribute that uniquely identifies a user on the LDAP server.
  <7> The attribute to use as the name of the user in the OpenShift group record.
  ====
  
  To run sync with the *_rfc2307_config.yaml_* file:
  
negative.code: When syncing groups with user-defined name mappings, the configuration file
  changes to contain these mappings as shown below.
  
  .LDAP Sync Configuration Using RFC 2307 Schema With User-Defined Name Mappings: *_rfc2307_config_user_defined.yaml_*
  ====
  [source,yaml]
  ----
  