Apply docs team style guide fixes

Style guide compliance improvements:
- Fix passive voice in opening paragraph ("This topic describes" -> direct)
- Replace weak verb "uses" with "includes" in component list
- Make list items parallel (all noun phrases describing components)
- Add cert-manager link in prerequisites section
- Remove future tense ("You'll use" -> "Use")
- Refine learning objectives to be more specific to procedures
- Move conditional phrase to sentence beginning for clarity

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: JakeSCahill

modules/deploy/pages/redpanda/kubernetes/k-stretch-clusters.adoc

@@ -6,11 +6,11 @@
 :page-toclevels: 1
 :page-topic-type: how-to
 :personas: platform_operator, platform_engineer
-:learning-objective-1: Deploy a Redpanda Stretch Cluster across multiple Kubernetes clusters
-:learning-objective-2: Configure cross-cluster networking for broker communication
-:learning-objective-3: Troubleshoot multicluster operator connectivity issues
+:learning-objective-1: Install multicluster operators with TLS certificates and peer configuration
+:learning-objective-2: Deploy StretchCluster and NodePool resources across Kubernetes clusters
+:learning-objective-3: Diagnose and resolve operator connectivity issues
 
-This topic describes how to deploy a Redpanda Stretch Cluster, a single logical cluster distributed across multiple Kubernetes clusters. Stretch Clusters provide high availability across regions with low-latency local access, automatic failover through Raft consensus, and unified cluster management.
+Deploy a Redpanda Stretch Cluster, a single logical cluster distributed across multiple Kubernetes clusters. Stretch Clusters provide high availability across regions with low-latency local access, automatic failover through Raft consensus, and unified cluster management.
 
 This beta version is available for testing and feedback. It is not supported by Redpanda and should not be used in production environments. To give feedback on beta releases, reach out to the Redpanda team in https://redpanda.com/slack[Redpanda Community Slack^].
 
@@ -22,10 +22,10 @@ After reading this page, you will be able to:
 
 CAUTION: **Clusters deployed using beta versions of the operator cannot be upgraded to the GA version.** You must delete and redeploy your cluster when upgrading from beta to GA. The StretchCluster and NodePool custom resources use the `v1alpha2` API version, which is subject to change.
 
-A Stretch Cluster deployment uses:
+A Stretch Cluster deployment includes:
 
-* **StretchCluster resource**: Defines cluster-wide configuration including Redpanda version, API settings, and networking mode
-* **NodePool resources**: Define broker groups within each Kubernetes cluster with replica counts, resources, and storage
+* **StretchCluster resource**: Cluster-wide configuration including Redpanda version, API settings, and networking mode
+* **NodePool resources**: Broker groups within each Kubernetes cluster with replica counts, resources, and storage
 * **Multicluster operators**: Redpanda Operator instances in each Kubernetes cluster that coordinate through Raft consensus
 * **Cross-cluster networking**: Direct broker-to-broker communication across Kubernetes clusters for Raft replication
 
@@ -55,7 +55,7 @@ Before deploying a Stretch Cluster, ensure you have:
 ** Access to the Kubernetes API servers of all peer clusters
 ** Valid kubeconfig with appropriate RBAC permissions for all clusters
 
-* **cert-manager**: Installed on all clusters for TLS certificate management
+* **cert-manager**: https://cert-manager.io/docs/installation/[cert-manager^] installed on all clusters for TLS certificate management
 
 * **TLS certificates for inter-operator communication**:
 ** ECDSA P-256 certificates (not RSA)
@@ -226,11 +226,11 @@ This command automatically:
 |Certificate organization field (default: `Redpanda`)
 |===
 +
-When the command completes, it prints a `multicluster.peers` block showing the peer addresses. You'll use these addresses in the Helm installation.
+When the command completes, it prints a `multicluster.peers` block showing the peer addresses. Use these addresses in the Helm installation.
 
 . Install the StretchCluster and NodePool CRDs on all clusters.
 +
-The StretchCluster and NodePool CRDs are installed by the Helm chart when you set `crds.experimental=true`. If you need to install them separately (for example, in GitOps workflows), you can apply them manually:
+The StretchCluster and NodePool CRDs are installed by the Helm chart when you set `crds.experimental=true`. For GitOps workflows or manual installation, apply the CRDs separately:
 +
 [,bash,subs="attributes+"]
 ----