Apply suggestions from code review

Co-authored-by: Nick <NickLarsenNZ@users.noreply.github.com>

Author: sbernauer

modules/contributor/pages/adr/ADR035-user-info-fetcher.adoc

@@ -21,18 +21,18 @@ We need to design a CRD change for users to enable the UIF.
 === Stand-alone CRD
 
 We could create a new CRD, e.g. UserInfoFetcher and have a controller for it that creates a DaemonSet.
-A OpaCluster would than be able to link to a UserInfoFetcher discovery ConfigMap.
+An OpaCluster would then be able to link to a UserInfoFetcher discovery ConfigMap.
 
 * Good, because a UIF instance can be shared across multiple OPA clusters -> Simple and improved caching
 * Bad, because OPA clusters would need to authenticate against UIF clusters.
 * Bad, because UIF might need some form of authorization as well
 
 === Integrate in OpaCluster
 
-Add a new section to OpaCluster that allows users to spin up a UIF as a sidecar within the Opa DaemonSet.
+Add a new section to OpaCluster that allows users to spin up a UIF as a sidecar within the Opa DaemonSet's Pods.
 
-The CRD is mostly copied from the `oidc` AuthenticationClass introduced in xref:adr/ADR032-oidc-support.adoc[] with the addition of needed credentials for Keycloak as well as the admin and user realm and a very simplistic cache.
-The cache will be probably extended in the future (e.g. max number of entries or users that should not be cached), which can be done in a non-breaking fashion below `spec.clusterConfig.userInfo.backend.keycloak.cache`.`
+The CRD is mostly copied from the `oidc` AuthenticationClass introduced in xref:adr/ADR032-oidc-support.adoc[] with the addition of needed credentials for Keycloak as well as the _admin_ and _user_ realms and a very simplistic cache.
+The cache might be extended in the future (e.g. to set the maximum number of cache entries or exempt particular users from being cached), which can be done in a non-breaking fashion below `spec.clusterConfig.userInfo.backend.keycloak.cache`.`
 
 [source,yaml]
 ----
@@ -72,7 +72,7 @@ stringData:
   clientSecret: user-info-fetcher-client-secret
 ----
 
-* Good, because only accessible via loopback to OPA clusters -> No authentication or authorization needed.
+* Good, because only accessible via the loopback network interface to OPA clusters -> No authentication or authorization needed.
 
 == Decision Outcome