Update content/vault/v1.7.x/content/docs/auth/ldap.mdx

Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>

Author: kevin-loehfelm

content/vault/v1.7.x/content/docs/auth/ldap.mdx

@@ -123,7 +123,12 @@ There are two alternate methods of resolving the user object used to authenticat
 - `discoverdn` (bool, optional) - If true, use anonymous bind to discover the bind DN of a user
 - `userdn` (string, optional) - Base DN under which to perform user search. Example: `ou=Users,dc=example,dc=com`
 - `userattr` (string, optional) - Attribute on user attribute object matching the username passed when authenticating. Examples: `sAMAccountName`, `cn`, `uid`
-- `deny_null_bind` (bool, optional) - 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. The default is `true`.
+- `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.
 - `anonymous_group_search` (bool, optional) - Use anonymous binds when performing LDAP group searches. Defaults to `false`.
 
 #### Binding - User Principal Name (AD)