diff --git a/docs/pages/deploy-a-cluster/high-availability.mdx b/docs/pages/deploy-a-cluster/high-availability.mdx
index 0737a0f509992..365b7da06cd82 100644
--- a/docs/pages/deploy-a-cluster/high-availability.mdx
+++ b/docs/pages/deploy-a-cluster/high-availability.mdx
@@ -108,6 +108,7 @@ services:
 | `3026` | HTTPS Kubernetes proxy |
 | `3036` | MySQL port |
 | `5432` | Postgres port |
+| `27017` | Mongo port |
 
 </TabItem>
 </Tabs>
diff --git a/docs/pages/management/guides/teleport-operator.mdx b/docs/pages/management/guides/teleport-operator.mdx
index cb306dcdfa92a..9ce1ea98380a7 100644
--- a/docs/pages/management/guides/teleport-operator.mdx
+++ b/docs/pages/management/guides/teleport-operator.mdx
@@ -240,10 +240,10 @@ $ kubectl logs "$PROXY_POD" -c operator
   To diagnose reconciliation issues, you will have to inspect all pods to find the one reconciling the resources.
 </Admonition>
 
-## Next Steps
+## Next steps
 
-Helm Chart parameters are documented in the [`teleport-cluster `Helm chart reference](../../reference/helm-reference/teleport-cluster.mdx).
+Helm Chart parameters are documented in the [`teleport-cluster` Helm chart reference](../../reference/helm-reference/teleport-cluster.mdx).
 
-See the [Helm Deployment guides](../../deploy-a-cluster/helm-deployments.mdx) detailing specific setups like running teleport on AWS or GCP.
+See the [Helm Deployment guides](../../deploy-a-cluster/helm-deployments.mdx) detailing specific setups like running Teleport on AWS or GCP.
 
 Check out [access controls documentation](../../access-controls/introduction.mdx)