Minor style fixes

Author: DMallare

docs/source/routing/self-hosted/containerization/kubernetes/quickstart.mdx

@@ -17,7 +17,7 @@ This guide shows how to:
 <ElasticNotice />
 
 <Note>
-For a production-grade self-hosted deployment Apollo recommends the [Apollo GraphOS Operator](https://www.apollographql.com/docs/apollo-operator).
+For a production-grade self-hosted deployment, Apollo recommends the [Apollo GraphOS Operator](/apollo-operator/).
 </Note>
 
 
@@ -132,9 +132,9 @@ helm install <name_for_install> --namespace <router-namespace> --set managedFede
 
 ## Consider using the Apollo GraphOS Operator
 
-The [Apollo GraphOS Operator](/apollo-operator/) offers an alternative method to deploy the router and manage your schema and subgraphs. The Operator provides declarative Kubernetes resources for managing routers, supergraphs, graph schemas, and subgraphs. It can simplify complex multi-service architectures.
+The [Apollo GraphOS Operator](/apollo-operator/) offers an alternative method to deploy the router and manage your schema and subgraphs. The Operator provides declarative Kubernetes resources to manage routers, supergraphs, graph schemas, and subgraphs. It simplifies complex multi-service architectures.
 
-The Operator offers different [workflow patterns](/apollo-operator/workflows/) depending on your infrastructure:
+The Operator supports different [workflow patterns](/apollo-operator/workflows/) based on your infrastructure:
 - Single-cluster setups for simpler deployments
 - Multi-cluster and hybrid configurations for distributed services
 - Deploy-only patterns for existing CI/CD workflows

docs/source/routing/self-hosted/index.mdx

@@ -24,16 +24,18 @@ For each version of the Apollo Router, Apollo provides:
 - [A Docker image](#container)
 - [A binary](#local-binary)
 
-## Kubernetes using the Apollo GraphOS Operator
+## Kubernetes
 
-For a production-grade self-hosted deployment Apollo recommends the [Apollo GraphOS Operator](/apollo-operator/). The Operator provides declarative Kubernetes resources for managing routers, supergraphs, graph schemas, and subgraphs. It can simplify complex multi-service architectures.
+### Apollo GraphOS Operator
 
-The Operator offers different [workflow patterns](/apollo-operator/workflows/) depending on your infrastructure:
+For a production-grade self-hosted deployment, Apollo recommends the [Apollo GraphOS Operator](/apollo-operator/). The Operator provides declarative Kubernetes resources to manage routers, supergraphs, graph schemas, and subgraphs. It simplifies complex multi-service architectures.
+
+The Operator supports different [workflow patterns](/apollo-operator/workflows/) based on your infrastructure:
 - Single-cluster setups for simpler deployments
 - Multi-cluster and hybrid configurations for distributed services
 - Deploy-only patterns for existing CI/CD workflows
 
-## Kubernetes using Helm
+### Helm
 
 Helm is a package manager for Kubernetes. Apollo provides a Helm chart with each release of Apollo Router in the GitHub Container Registry. Since router v0.14.0, Apollo has released each router Helm chart as an Open Container Initiative (OCI) image in `oci://ghcr.io/apollographql/helm-charts/router`.