Apply suggestions from code review

Co-authored-by: Sarah Chavis <[email protected]>

Author: fairclothjm

content/vault/v1.18.x/content/docs/secrets/ldap.mdx

@@ -73,28 +73,28 @@ There are many object classes that provide `userPassword` including for example:
 
 ### Resource access control facility (RACF)
 
-To manage credentials for IBM's Resource Access Control Facility (RACF), you
-must configure the LDAP secrets engine with the `racf` schema. This enables
-specific behaviors required for RACF compatibility.
+To manage credentials for an IBM Resource Access Control Facility (RACF), 
+configure the LDAP secrets engine with the `racf` schema to enable the
+behaviors required for RACF compatibility.
 
-#### Credential Type: Password vs. Password Phrase
+#### Password vs. password phrase credentials
 
-The engine can manage both traditional 8-character passwords and modern, longer
-password phrases. This is controlled by the [`credential_type`](/vault/api-docs/secret/ldap#credential_type)
-parameter:
+The LDAP plugin supports traditional 8-character passwords and modern,
+longer password phrases through th
+[`credential_type`](/vault/api-docs/secret/ldap#credential_type) parameter:
 
-- `password` (Default): The engine will generate and manage standard RACF passwords.
+- `password` (Default): Configure the plugin to generate and manage standard RACF passwords.
 
-- `phrase`: The engine will generate and manage case-sensitive password phrases.
+- `phrase`: Configure the plugin to generate and manage case-sensitive password phrases.
 
-#### Configuring Password Rules
+#### Configure password rules
 
-The complexity rules for generated credentials, such as length, are not
-controlled by the RACF schema itself. Instead, you must define and link a
-standard Vault [password policy](/vault/docs/concepts/password-policies).
-This allows you to enforce site-specific complexity requirements.
+The RACF schema does not control the credential complexity rules directly.
+To enforce site-specific complexity requirements, define and link a
+standard Vault [password policy](/vault/docs/concepts/password-policies)
+to your RACF schema.
 
-#### Example Configuration
+#### Example configuration
 
 The following example configures the LDAP engine for RACF, sets it to manage
 password phrases, and links a password policy to enforce length and

content/vault/v1.19.x/content/docs/secrets/ldap.mdx

@@ -73,28 +73,29 @@ There are many object classes that provide `userPassword` including for example:
 
 ### Resource access control facility (RACF)
 
-To manage credentials for IBM's Resource Access Control Facility (RACF), you
-must configure the LDAP secrets engine with the `racf` schema. This enables
-specific behaviors required for RACF compatibility.
+To manage credentials for an IBM Resource Access Control Facility (RACF), 
+configure the LDAP secrets engine with the `racf` schema to enable the
+behaviors required for RACF compatibility.
 
-#### Credential Type: Password vs. Password Phrase
+#### Password vs. password phrase credentials
 
-The engine can manage both traditional 8-character passwords and modern, longer
-password phrases. This is controlled by the [`credential_type`](/vault/api-docs/secret/ldap#credential_type)
-parameter:
+The LDAP plugin supports traditional 8-character passwords and modern,
+longer password phrases through th
+[`credential_type`](/vault/api-docs/secret/ldap#credential_type) parameter:
 
-- `password` (Default): The engine will generate and manage standard RACF passwords.
+- `password` (Default): Configure the plugin to generate and manage standard RACF passwords.
+- `phrase`: Configure the plugin to generate and manage case-sensitive password phrases.
 
-- `phrase`: The engine will generate and manage case-sensitive password phrases.
 
-#### Configuring Password Rules
+#### Configure password rules
 
-The complexity rules for generated credentials, such as length, are not
-controlled by the RACF schema itself. Instead, you must define and link a
-standard Vault [password policy](/vault/docs/concepts/password-policies).
-This allows you to enforce site-specific complexity requirements.
+The RACF schema does not control the credential complexity rules directly.
+To enforce site-specific complexity requirements, define and link a
+standard Vault [password policy](/vault/docs/concepts/password-policies)
+to your RACF schema.
 
-#### Example Configuration
+
+#### Example configuration
 
 The following example configures the LDAP engine for RACF, sets it to manage
 password phrases, and links a password policy to enforce length and

content/vault/v1.20.x/content/docs/secrets/ldap.mdx

@@ -73,28 +73,29 @@ There are many object classes that provide `userPassword` including for example:
 
 ### Resource access control facility (RACF)
 
-To manage credentials for IBM's Resource Access Control Facility (RACF), you
-must configure the LDAP secrets engine with the `racf` schema. This enables
-specific behaviors required for RACF compatibility.
+To manage credentials for an IBM Resource Access Control Facility (RACF), 
+configure the LDAP secrets engine with the `racf` schema to enable the
+behaviors required for RACF compatibility.
 
-#### Credential Type: Password vs. Password Phrase
+#### Password vs. password phrase credentials
 
-The engine can manage both traditional 8-character passwords and modern, longer
-password phrases. This is controlled by the [`credential_type`](/vault/api-docs/secret/ldap#credential_type)
-parameter:
+The LDAP plugin supports traditional 8-character passwords and modern,
+longer password phrases through th
+[`credential_type`](/vault/api-docs/secret/ldap#credential_type) parameter:
 
-- `password` (Default): The engine will generate and manage standard RACF passwords.
+- `password` (Default): Configure the plugin to generate and manage standard RACF passwords.
+- `phrase`: Configure the plugin to generate and manage case-sensitive password phrases.
 
-- `phrase`: The engine will generate and manage case-sensitive password phrases.
 
-#### Configuring Password Rules
+#### Configure password rules
 
-The complexity rules for generated credentials, such as length, are not
-controlled by the RACF schema itself. Instead, you must define and link a
-standard Vault [password policy](/vault/docs/concepts/password-policies).
-This allows you to enforce site-specific complexity requirements.
+The RACF schema does not control the credential complexity rules directly.
+To enforce site-specific complexity requirements, define and link a
+standard Vault [password policy](/vault/docs/concepts/password-policies)
+to your RACF schema.
 
-#### Example Configuration
+
+#### Example configuration
 
 The following example configures the LDAP engine for RACF, sets it to manage
 password phrases, and links a password policy to enforce length and

content/vault/v1.21.x (rc)/content/docs/secrets/ldap.mdx

@@ -73,28 +73,29 @@ There are many object classes that provide `userPassword` including for example:
 
 ### Resource access control facility (RACF)
 
-To manage credentials for IBM's Resource Access Control Facility (RACF), you
-must configure the LDAP secrets engine with the `racf` schema. This enables
-specific behaviors required for RACF compatibility.
+To manage credentials for an IBM Resource Access Control Facility (RACF), 
+configure the LDAP secrets engine with the `racf` schema to enable the
+behaviors required for RACF compatibility.
 
-#### Credential Type: Password vs. Password Phrase
+#### Password vs. password phrase credentials
 
-The engine can manage both traditional 8-character passwords and modern, longer
-password phrases. This is controlled by the [`credential_type`](/vault/api-docs/secret/ldap#credential_type)
-parameter:
+The LDAP plugin supports traditional 8-character passwords and modern,
+longer password phrases through th
+[`credential_type`](/vault/api-docs/secret/ldap#credential_type) parameter:
 
-- `password` (Default): The engine will generate and manage standard RACF passwords.
+- `password` (Default): Configure the plugin to generate and manage standard RACF passwords.
+- `phrase`: Configure the plugin to generate and manage case-sensitive password phrases.
 
-- `phrase`: The engine will generate and manage case-sensitive password phrases.
 
-#### Configuring Password Rules
+#### Configure password rules
 
-The complexity rules for generated credentials, such as length, are not
-controlled by the RACF schema itself. Instead, you must define and link a
-standard Vault [password policy](/vault/docs/concepts/password-policies).
-This allows you to enforce site-specific complexity requirements.
+The RACF schema does not control the credential complexity rules directly.
+To enforce site-specific complexity requirements, define and link a
+standard Vault [password policy](/vault/docs/concepts/password-policies)
+to your RACF schema.
 
-#### Example Configuration
+
+#### Example configuration
 
 The following example configures the LDAP engine for RACF, sets it to manage
 password phrases, and links a password policy to enforce length and