Making some minor fixes

Author: bergerhoffer

modules/installation-alibaba-config-yaml.adoc

@@ -41,7 +41,7 @@ metadata:
   - 172.30.0.0/16
 platform:
   alibabacloud:
-    defaultMachinePlatform: <2> 
+    defaultMachinePlatform: <2>
       instanceType: ecs.g6.xlarge
       systemDiskCategory: cloud_efficiency
       systemDiskSize: 200
@@ -54,8 +54,7 @@ sshKey: |
 ----
 <1> Required. The installation program prompts you for a cluster name.
 <2> Optional. Specify parameters for machine pools that do not define their own platform configuration.
-<3> Required. The installation program prompts you for the the region to deploy the cluster to.
+<3> Required. The installation program prompts you for the region to deploy the cluster to.
 <4> Optional. Specify an existing resource group where the cluster should be installed.
 <5> Required. The installation program prompts you for the pull secret.
-<6> Optional. The installation program prompts you for the SSH key value that you use to access the machines in your cluster. 
-
+<6> Optional. The installation program prompts you for the SSH key value that you use to access the machines in your cluster.

modules/sdpolicy-networking.adoc

@@ -31,7 +31,7 @@ Custom domains and subdomains are not available for the platform service routes,
 * External control plane load balancer for Red Hat that is reserved for cluster management by Red Hat. Access is strictly controlled, and communication is only possible from allowlisted bastion hosts.
 * Default router/ingress load balancer that is the default application load balancer, denoted by `apps` in the URL. The default load balancer can be configured in {cluster-manager} to be either publicly accessible over the internet, or only privately accessible over a pre-existing private connection. All application routes on the cluster are exposed on this default router load balancer, including cluster services such as the logging UI, metrics API, and registry.
 * Optional: Secondary router/ingress load balancer that is a secondary application load balancer, denoted by `apps2` in the URL. The secondary load balancer can be configured in {cluster-manager} to be either publicly accessible over the internet, or only privately accessible over a pre-existing private connection. If a 'Label match' is configured for this router load balancer, then only application routes matching this label will be exposed on this router load balancer, otherwise all application routes are also exposed on this router load balancer.
-* Optional: Load balancers for services that can can be mapped to a service running on {product-title} to enable advanced ingress features, such as non-HTTP/SNI traffic or the use of non-standard ports. These can be purchased in groups of 4 for standard clusters, or they can be provisioned without charge in Customer Cloud Subscription (CCS) clusters; however, each AWS account has a quota that link:https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-limits.html[limits the number of Classic Load Balancers] that can be used within each cluster.
+* Optional: Load balancers for services that can be mapped to a service running on {product-title} to enable advanced ingress features, such as non-HTTP/SNI traffic or the use of non-standard ports. These can be purchased in groups of 4 for standard clusters, or they can be provisioned without charge in Customer Cloud Subscription (CCS) clusters; however, each AWS account has a quota that link:https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/elb-limits.html[limits the number of Classic Load Balancers] that can be used within each cluster.
 
 [id="network-usage{context}"]
 == Network usage

serverless/admin_guide/serverless-configuration.adoc

@@ -21,7 +21,8 @@ The `spec.config` in the Knative custom resources have one `<name>` entry for ea
 
 You can specify that the `KnativeServing` custom resource uses the `config-domain` config map  as follows:
 
-```yaml
+[source,yaml]
+----
 apiVersion: operator.knative.dev/v1alpha1
 kind: KnativeServing
 metadata:
@@ -34,12 +35,13 @@ spec:
         selector:
           app: prod
       example.com: ""
-```
+----
 <1> Specifies the `config-domain` config map.
 
 You can apply values to multiple config maps. This example sets `stable-window` to 60s in the `config-autoscaler` config map, as well as specifying the `config-domain` config map:
 
-```yaml
+[source,yaml]
+----
 apiVersion: operator.knative.dev/v1alpha1
 kind: KnativeServing
 metadata:
@@ -54,6 +56,6 @@ spec:
       example.com: ""
     autoscaler: <2>
       stable-window: "60s"
-```
+----
 <1> Specifies the `config-domain` config map.
 <2> Specifies the `stable-window` setting in the `config-autoscaler` config map.