Update style on API docs

Author: kevin-loehfelm

content/vault/v1.13.x/content/api-docs/auth/ldap.mdx

@@ -65,12 +65,12 @@ This endpoint configures the LDAP auth method.
   username passed when authenticating. Examples: `sAMAccountName`, `cn`, `uid`
 - `discoverdn` `(bool: false)` – Use anonymous bind to discover the bind DN of a
   user.
-- `deny_null_bind` `(bool: true)` – By default, Vault will prevent LDAP authentication 
-  attempts where the user provides an empty password (null binds). Setting this parameter 
-  to false allows Vault to support LDAP anonymous bind operations, which may be required 
-  for certain directory configurations that use anonymous search or discovery. When set to 
-  false, Vault defers the handling of empty-password authentication attempts to the LDAP 
-  server.
+- `deny_null_bind` `(bool: true)` – By default, Vault prevents LDAP authentication 
+  attempts when the user provides an empty password (null binds). Setting
+  `deny_null_bind` to `false` tells Vault to defer the handling of empty-password
+  authentication attempts to the LDAP server. You may want to allow LDAP
+  anonymous bind operations for directory configurations using anonymous search
+  or discovery.
 - `upndomain` `(string: "")` – The userPrincipalDomain used to construct the UPN
   string for the authenticating user. The constructed UPN will appear as
   `[username]@UPNDomain`. Example: `example.com`, which will cause vault to bind

content/vault/v1.14.x/content/api-docs/auth/ldap.mdx

@@ -65,12 +65,12 @@ This endpoint configures the LDAP auth method.
   username passed when authenticating. Examples: `sAMAccountName`, `cn`, `uid`
 - `discoverdn` `(bool: false)` – Use anonymous bind to discover the bind DN of a
   user.
-- `deny_null_bind` `(bool: true)` – By default, Vault will prevent LDAP authentication 
-  attempts where the user provides an empty password (null binds). Setting this parameter 
-  to false allows Vault to support LDAP anonymous bind operations, which may be required 
-  for certain directory configurations that use anonymous search or discovery. When set to 
-  false, Vault defers the handling of empty-password authentication attempts to the LDAP 
-  server.
+- `deny_null_bind` `(bool: true)` – By default, Vault prevents LDAP authentication 
+  attempts when the user provides an empty password (null binds). Setting
+  `deny_null_bind` to `false` tells Vault to defer the handling of empty-password
+  authentication attempts to the LDAP server. You may want to allow LDAP
+  anonymous bind operations for directory configurations using anonymous search
+  or discovery.
 - `upndomain` `(string: "")` – The userPrincipalDomain used to construct the UPN
   string for the authenticating user. The constructed UPN will appear as
   `[username]@UPNDomain`. Example: `example.com`, which will cause vault to bind

content/vault/v1.15.x/content/api-docs/auth/ldap.mdx

@@ -65,12 +65,12 @@ This endpoint configures the LDAP auth method.
   username passed when authenticating. Examples: `sAMAccountName`, `cn`, `uid`
 - `discoverdn` `(bool: false)` – Use anonymous bind to discover the bind DN of a
   user.
-- `deny_null_bind` `(bool: true)` – By default, Vault will prevent LDAP authentication 
-  attempts where the user provides an empty password (null binds). Setting this parameter 
-  to false allows Vault to support LDAP anonymous bind operations, which may be required 
-  for certain directory configurations that use anonymous search or discovery. When set to 
-  false, Vault defers the handling of empty-password authentication attempts to the LDAP 
-  server.
+- `deny_null_bind` `(bool: true)` – By default, Vault prevents LDAP authentication 
+  attempts when the user provides an empty password (null binds). Setting
+  `deny_null_bind` to `false` tells Vault to defer the handling of empty-password
+  authentication attempts to the LDAP server. You may want to allow LDAP
+  anonymous bind operations for directory configurations using anonymous search
+  or discovery.
 - `upndomain` `(string: "")` – The userPrincipalDomain used to construct the UPN
   string for the authenticating user. The constructed UPN will appear as
   `[username]@UPNDomain`. Example: `example.com`, which will cause vault to bind

content/vault/v1.16.x/content/api-docs/auth/ldap.mdx

@@ -65,12 +65,12 @@ This endpoint configures the LDAP auth method.
   username passed when authenticating. Examples: `sAMAccountName`, `cn`, `uid`
 - `discoverdn` `(bool: false)` – Use anonymous bind to discover the bind DN of a
   user.
-- `deny_null_bind` `(bool: true)` – By default, Vault will prevent LDAP authentication 
-  attempts where the user provides an empty password (null binds). Setting this parameter 
-  to false allows Vault to support LDAP anonymous bind operations, which may be required 
-  for certain directory configurations that use anonymous search or discovery. When set to 
-  false, Vault defers the handling of empty-password authentication attempts to the LDAP 
-  server.
+- `deny_null_bind` `(bool: true)` – By default, Vault prevents LDAP authentication 
+  attempts when the user provides an empty password (null binds). Setting
+  `deny_null_bind` to `false` tells Vault to defer the handling of empty-password
+  authentication attempts to the LDAP server. You may want to allow LDAP
+  anonymous bind operations for directory configurations using anonymous search
+  or discovery.
 - `upndomain` `(string: "")` – The userPrincipalDomain used to construct the UPN
   string for the authenticating user. The constructed UPN will appear as
   `[username]@UPNDomain`. Example: `example.com`, which will cause vault to bind

content/vault/v1.17.x/content/api-docs/auth/ldap.mdx

@@ -65,12 +65,12 @@ This endpoint configures the LDAP auth method.
   username passed when authenticating. Examples: `sAMAccountName`, `cn`, `uid`
 - `discoverdn` `(bool: false)` – Use anonymous bind to discover the bind DN of a
   user.
-- `deny_null_bind` `(bool: true)` – By default, Vault will prevent LDAP authentication 
-  attempts where the user provides an empty password (null binds). Setting this parameter 
-  to false allows Vault to support LDAP anonymous bind operations, which may be required 
-  for certain directory configurations that use anonymous search or discovery. When set to 
-  false, Vault defers the handling of empty-password authentication attempts to the LDAP 
-  server.
+- `deny_null_bind` `(bool: true)` – By default, Vault prevents LDAP authentication 
+  attempts when the user provides an empty password (null binds). Setting
+  `deny_null_bind` to `false` tells Vault to defer the handling of empty-password
+  authentication attempts to the LDAP server. You may want to allow LDAP
+  anonymous bind operations for directory configurations using anonymous search
+  or discovery.
 - `upndomain` `(string: "")` – The userPrincipalDomain used to construct the UPN
   string for the authenticating user. The constructed UPN will appear as
   `[username]@UPNDomain`. Example: `example.com`, which will cause vault to bind

content/vault/v1.18.x/content/api-docs/auth/ldap.mdx

@@ -65,12 +65,12 @@ This endpoint configures the LDAP auth method.
   username passed when authenticating. Examples: `sAMAccountName`, `cn`, `uid`
 - `discoverdn` `(bool: false)` – Use anonymous bind to discover the bind DN of a
   user.
-- `deny_null_bind` `(bool: true)` – By default, Vault will prevent LDAP authentication 
-  attempts where the user provides an empty password (null binds). Setting this parameter 
-  to false allows Vault to support LDAP anonymous bind operations, which may be required 
-  for certain directory configurations that use anonymous search or discovery. When set to 
-  false, Vault defers the handling of empty-password authentication attempts to the LDAP 
-  server.
+- `deny_null_bind` `(bool: true)` – By default, Vault prevents LDAP authentication 
+  attempts when the user provides an empty password (null binds). Setting
+  `deny_null_bind` to `false` tells Vault to defer the handling of empty-password
+  authentication attempts to the LDAP server. You may want to allow LDAP
+  anonymous bind operations for directory configurations using anonymous search
+  or discovery.
 - `upndomain` `(string: "")` – The userPrincipalDomain used to construct the UPN
   string for the authenticating user. The constructed UPN will appear as
   `[username]@UPNDomain`. Example: `example.com`, which will cause vault to bind

content/vault/v1.19.x/content/api-docs/auth/ldap.mdx

@@ -65,12 +65,12 @@ This endpoint configures the LDAP auth method.
   username passed when authenticating. Examples: `sAMAccountName`, `cn`, `uid`
 - `discoverdn` `(bool: false)` – Use anonymous bind to discover the bind DN of a
   user.
-- `deny_null_bind` `(bool: true)` – By default, Vault will prevent LDAP authentication 
-  attempts where the user provides an empty password (null binds). Setting this parameter 
-  to false allows Vault to support LDAP anonymous bind operations, which may be required 
-  for certain directory configurations that use anonymous search or discovery. When set to 
-  false, Vault defers the handling of empty-password authentication attempts to the LDAP 
-  server.
+- `deny_null_bind` `(bool: true)` – By default, Vault prevents LDAP authentication 
+  attempts when the user provides an empty password (null binds). Setting
+  `deny_null_bind` to `false` tells Vault to defer the handling of empty-password
+  authentication attempts to the LDAP server. You may want to allow LDAP
+  anonymous bind operations for directory configurations using anonymous search
+  or discovery.
 - `upndomain` `(string: "")` – The userPrincipalDomain used to construct the UPN
   string for the authenticating user. The constructed UPN will appear as
   `[username]@UPNDomain`. Example: `example.com`, which will cause vault to bind

content/vault/v1.20.x/content/api-docs/auth/ldap.mdx

@@ -65,12 +65,12 @@ This endpoint configures the LDAP auth method.
   username passed when authenticating. Examples: `sAMAccountName`, `cn`, `uid`
 - `discoverdn` `(bool: false)` – Use anonymous bind to discover the bind DN of a
   user.
-- `deny_null_bind` `(bool: true)` – By default, Vault will prevent LDAP authentication 
-  attempts where the user provides an empty password (null binds). Setting this parameter 
-  to false allows Vault to support LDAP anonymous bind operations, which may be required 
-  for certain directory configurations that use anonymous search or discovery. When set to 
-  false, Vault defers the handling of empty-password authentication attempts to the LDAP 
-  server.
+- `deny_null_bind` `(bool: true)` – By default, Vault prevents LDAP authentication 
+  attempts when the user provides an empty password (null binds). Setting
+  `deny_null_bind` to `false` tells Vault to defer the handling of empty-password
+  authentication attempts to the LDAP server. You may want to allow LDAP
+  anonymous bind operations for directory configurations using anonymous search
+  or discovery.
 - `upndomain` `(string: "")` – The userPrincipalDomain used to construct the UPN
   string for the authenticating user. The constructed UPN will appear as
   `[username]@UPNDomain`. Example: `example.com`, which will cause vault to bind

content/vault/v1.4.x/content/api-docs/auth/ldap/index.mdx

@@ -57,12 +57,12 @@ This endpoint configures the LDAP auth method.
   username passed when authenticating. Examples: `sAMAccountName`, `cn`, `uid`
 - `discoverdn` `(bool: false)` – Use anonymous bind to discover the bind DN of a
   user.
-- `deny_null_bind` `(bool: true)` – By default, Vault will prevent LDAP authentication 
-  attempts where the user provides an empty password (null binds). Setting this parameter 
-  to false allows Vault to support LDAP anonymous bind operations, which may be required 
-  for certain directory configurations that use anonymous search or discovery. When set to 
-  false, Vault defers the handling of empty-password authentication attempts to the LDAP 
-  server.
+- `deny_null_bind` `(bool: true)` – By default, Vault prevents LDAP authentication 
+  attempts when the user provides an empty password (null binds). Setting
+  `deny_null_bind` to `false` tells Vault to defer the handling of empty-password
+  authentication attempts to the LDAP server. You may want to allow LDAP
+  anonymous bind operations for directory configurations using anonymous search
+  or discovery.
 - `upndomain` `(string: "")` – The userPrincipalDomain used to construct the UPN
   string for the authenticating user. The constructed UPN will appear as
   `[username]@UPNDomain`. Example: `example.com`, which will cause vault to bind

content/vault/v1.5.x/content/api-docs/auth/ldap/index.mdx

@@ -61,12 +61,12 @@ This endpoint configures the LDAP auth method.
   username passed when authenticating. Examples: `sAMAccountName`, `cn`, `uid`
 - `discoverdn` `(bool: false)` – Use anonymous bind to discover the bind DN of a
   user.
-- `deny_null_bind` `(bool: true)` – By default, Vault will prevent LDAP authentication 
-  attempts where the user provides an empty password (null binds). Setting this parameter 
-  to false allows Vault to support LDAP anonymous bind operations, which may be required 
-  for certain directory configurations that use anonymous search or discovery. When set to 
-  false, Vault defers the handling of empty-password authentication attempts to the LDAP 
-  server.
+- `deny_null_bind` `(bool: true)` – By default, Vault prevents LDAP authentication 
+  attempts when the user provides an empty password (null binds). Setting
+  `deny_null_bind` to `false` tells Vault to defer the handling of empty-password
+  authentication attempts to the LDAP server. You may want to allow LDAP
+  anonymous bind operations for directory configurations using anonymous search
+  or discovery.
 - `upndomain` `(string: "")` – The userPrincipalDomain used to construct the UPN
   string for the authenticating user. The constructed UPN will appear as
   `[username]@UPNDomain`. Example: `example.com`, which will cause vault to bind