Apply suggestions from code review

Co-authored-by: Natalia Ivakina <82437520+NataliaIvakina@users.noreply.github.com>

Author: NataliaIvakina

modules/ROOT/pages/monitoring/logging.adoc

@@ -1304,7 +1304,7 @@ Included when xref:configuration/configuration-settings.adoc#config_db.logs.quer
 | The username of the user executing the query.
 Either same as `authenticatedUser` or an impersonated user.
 
-| authenticatedUser footnote:[When SSO is enabled, the username is determined either by the xref:configuration/configuration-settings.adoc#config_dbms.security.oidc.-provider-.claims.username[`dbms.security.oidc.<provider>.claims.username`] setting.
+| authenticatedUser footnote:[When SSO is enabled, the username is determined by the xref:configuration/configuration-settings.adoc#config_dbms.security.oidc.-provider-.claims.username[`dbms.security.oidc.<provider>.claims.username`] setting.
 If LDAP is configured, Neo4j determines the username string using one of two settings: xref:configuration/configuration-settings.adoc#config_dbms.security.ldap.authentication.user_dn_template[`dbms.security.ldap.authentication.user_dn_template`] or xref:configuration/configuration-settings.adoc#config_dbms.security.ldap.authentication.attribute[`dbms.security.ldap.authentication.attribute`].
 For both SSO and LDAP, if local user mapping is required (`dbms.security.require_local_user=true`), the log records the mapped local username instead of the external identity string.
 If authentication is controlled on a user level via Cypher statements, the username is defined directly inside the `system` database using native user creation queries: `CREATE USER 'name'`.]