Minor HA guide fixes (#27436)

Signed-off-by: Michal Hajas <mhajas@redhat.com>

docs/guides/high-availability/bblocks-active-passive-sync.adoc

@@ -58,7 +58,7 @@ A clustered deployment of {project_name} in each site, connected to an external
 
 == Load balancer
 
-A load balancer which checks the `/lb-check` URl of the {project_name} deployment in each site.
+A load balancer which checks the `/lb-check` URL of the {project_name} deployment in each site.
 
 *Blueprint:* <@links.ha id="deploy-aws-route53-loadbalancer"/>.
 

docs/guides/high-availability/concepts-infinispan-cli-batch.adoc

@@ -15,7 +15,7 @@ When interacting with an external {jdgserver_name} in Kubernetes, the `Batch` CR
 Use this when automating interactions on Kubernetes.
 This avoids providing usernames and passwords and checking shell script outputs and their status.
 
-For human interactive interactions, the CLI shell might still be a better fit.
+For human interactions, the CLI shell might still be a better fit.
 
 == Example
 

docs/guides/high-availability/deploy-aws-route53-loadbalancer.adoc

@@ -6,7 +6,7 @@ title="Deploy an AWS Route 53 loadbalancer"
 summary="Building block for a loadbalancer"
 tileVisible="false" >
 
-This topic describes the procedure required to configure DNS based failover for Multi-AZ {project_name} clusters using AWS Route53 for an active/passive setup. These instructions are intended for used with the setup described in the <@links.ha id="concepts-active-passive-sync"/> {section}.
+This topic describes the procedure required to configure DNS based failover for Multi-AZ {project_name} clusters using AWS Route53 for an active/passive setup. These instructions are intended to be used with the setup described in the <@links.ha id="concepts-active-passive-sync"/> {section}.
 Use it together with the other building blocks outlined in the <@links.ha id="bblocks-active-passive-sync"/> {section}.
 
 include::partials/blueprint-disclaimer.adoc[]

docs/guides/high-availability/deploy-keycloak-kubernetes.adoc

@@ -36,7 +36,7 @@ include::examples/generated/keycloak.yaml[tag=keycloak]
 Adjust this number to meet the needs of your system.
 As most requests will not touch the database due to the {project_name} embedded cache, this change can server several hundreds of requests per second.
 See the <@links.ha id="concepts-database-connections" /> {section} for details.
-<2> Specify the URL to your custom {project_name} image. If your image is optimized, set the `startOptimized` flag to `true.
+<2> Specify the URL to your custom {project_name} image. If your image is optimized, set the `startOptimized` flag to `true`.
 <3> Enable additional features for multi-site support like the loadbalancer probe `/lb-check`.
 <4> XA transactions are not supported by the https://github.com/awslabs/aws-advanced-jdbc-wrapper/releases/[Amazon Web Services JDBC Driver].
 <5> To be able to analyze the system under load, enable the metrics endpoint.
@@ -65,7 +65,7 @@ To enable load shedding, limit the number of queued requests.
 [source,yaml,indent=0]
 ----
 spec:
- additionalOptions:
+  additionalOptions:
 include::examples/generated/keycloak.yaml[tag=keycloak-queue-size]
 ----
 All exceeding requests are served with an HTTP 503.
@@ -81,13 +81,13 @@ Add the following supplementary configuration under the `spec` in the {project_n
 [source,yaml,subs="attributes+"]
 ----
 spec:
-    ingress:
-        enabled: true
-        annotations:
-          # When running load tests, disable sticky sessions on the OpenShift HAProxy router
-          # to avoid receiving all requests on a single {project_name} Pod.
-          haproxy.router.openshift.io/balance: roundrobin
-          haproxy.router.openshift.io/disable_cookies: 'true'
+  ingress:
+    enabled: true
+    annotations:
+      # When running load tests, disable sticky sessions on the OpenShift HAProxy router
+      # to avoid receiving all requests on a single {project_name} Pod.
+      haproxy.router.openshift.io/balance: roundrobin
+      haproxy.router.openshift.io/disable_cookies: 'true'
 ----
 
 </@tmpl.guide>

docs/guides/high-availability/partials/infinispan/infinispan-credentials.adoc

@@ -4,7 +4,7 @@
 {project_name} needs this credential to be able to authenticate with the Infinispan cluster.
 The following `identities.yaml` file sets the username and password with admin permissions
 +
-[source,yam,subs="+attributes"]
+[source,yaml,subs="+attributes"]
 ----
 credentials:
   - username: developer