pr review comments

Author: phil198

modules/ROOT/pages/authentication-authorization/ldap-integration.adoc

@@ -434,12 +434,12 @@ CREATE USER alice
 SET AUTH PROVIDER 'ldap' { SET ID 'cn=alice,ou=engineering,dc=example,dc=com' }
 ----
 
-Then natively grant the `ANALYST` role to the user:
+Then natively grant the `READER` role to the user:
 ----
-GRANT ROLE ANALYST TO alice
+GRANT ROLE READER TO alice
 ----
 
-This will allow the user to authenticate using `ldap` and receive the `ANALYST` role from the `native` provider.
+This will allow the user to authenticate using `ldap` and receive the `READER` role from the `native` provider.
 
 It would also be possible to give the user the union of roles from `ldap` *and*  `native` roles by setting `ldap` as an authorization provider too:
 

modules/ROOT/pages/authentication-authorization/sso-integration.adoc

@@ -329,7 +329,7 @@ dbms.security.authorization_providers=native
 Then create a user with a `mysso` Auth Provider:
 ----
 CREATE USER jake
-SET AUTH 'oidc-mysso' {SET ID 'jakesUniqueMySsoId'} // this must match the claim that you configured via dbms.security.oidc.mysso.claims.username
+SET AUTH 'oidc-mysso' {SET ID 'jakesUniqueMySsoId'} // `jakesUniqueMySsoId` must match the value of the claim that you configured via dbms.security.oidc.mysso.claims.username
 ----
 
 Then natively grant the `READER` role to the user:

modules/ROOT/pages/tutorial/tutorial-sso-configuration.adoc

@@ -142,7 +142,7 @@ For example to create a user `jake` who can authenticate using native or Okta, a
 ----
 CREATE USER jake
 SET HOME DATABASE 'jakesHomeDb'
-SET AUTH 'oidc-okta' {SET ID 'jakesUniqueOktaUserId'} // this must match the claim that you configured via dbms.security.oidc.okta.claims.username
+SET AUTH 'oidc-okta' {SET ID 'jakesUniqueOktaUserId'} // `jakesUniqueOktaUserId` must match the value of the claim that you configured via dbms.security.oidc.okta.claims.username
 SET AUTH 'native' {SET PASSWORD 'changeme' SET PASSWORD CHANGE REQUIRED}
 ----
 
@@ -334,7 +334,7 @@ For example to create a user `jake` who can authenticate and authorize using Ent
 ----
 CREATE USER jake
 SET HOME DATABASE 'jakesHomeDb'
-SET AUTH 'oidc-okta' {SET ID 'jakesUniqueEntraUserId'} // this must match the claim that you configured via dbms.security.oidc.azure.claims.username
+SET AUTH 'oidc-okta' {SET ID 'jakesUniqueEntraUserId'} // `jakesUniqueEntraUserId` must match the value of the claim that you configured via dbms.security.oidc.azure.claims.username
 ----
 
 See xref:authentication-authorization/sso-integration.adoc#auth-sso-auth-providers[SSO integration] for further examples.
@@ -401,7 +401,7 @@ dbms.security.require_local_user=true
 ----
 CREATE USER jake
 SET HOME DATABASE 'jakesHomeDb'
-SET AUTH 'oidc-google' {SET ID 'jakesUniqueGoogleUserId'} // this must match the claim that you configured via dbms.security.oidc.google.claims.username
+SET AUTH 'oidc-google' {SET ID 'jakesUniqueGoogleUserId'} // `jakesUniqueGoogleUserId` must match the value of the claim that you configured via dbms.security.oidc.google.claims.username
 ----
 
 .. Grant the user roles using native authorization.
@@ -453,7 +453,7 @@ dbms.security.authentication_providers=oidc-google
 
 [source, cypher, role=noplay]
 ----
-CREATE USER jakesUniqueGoogleUserId // this must match the claim that you configured via dbms.security.oidc.google.claims.username
+CREATE USER jakesUniqueGoogleUserId // `jakesUniqueGoogleUserId` must match the value of the claim that you configured via dbms.security.oidc.google.claims.username
 SET HOME DATABASE 'jakesHomeDb'
 SET PASSWORD 'secretpassword' SET PASSWORD CHANGE NOT
 REQUIRED