apply suggestions

Co-authored-by: Benedikt Rollik <[email protected]>

Author: louisportay

pages/kubernetes/how-to/recover-space-etcd.mdx

@@ -1,10 +1,10 @@
 ---
 meta:
-title: Recovering ETCD Database space for a Kapsule/Kosmos cluster
-description: Learn how to reclaim Database space for your Kubernetes Kapsule and Kosmos clusters to stay below your quota.
+title: Recovering ETCD database space for a Kapsule/Kosmos cluster
+description: Learn how to reclaim database space for your Kubernetes Kapsule and Kosmos clusters to stay below your quota.
 content:
-h1: Recovering ETCD Database space for a Kapsule/Kosmos cluster
-paragraph: Learn how to reclaim Database space for your Kubernetes Kapsule and Kosmos clusters to stay below your quota.
+h1: Recovering ETCD database space for a Kapsule/Kosmos cluster
+paragraph: Learn how to reclaim database space for your Kubernetes Kapsule and Kosmos clusters to stay below your quota.
 tags: kubernetes kapsule kosmos etcd
 dates:
 validation: 2025-04-01
@@ -40,7 +40,7 @@ This guide helps you to free up space on your database to avoid reaching this li
   jobs                                                                    batch/v1                             true         Job
   [...]
   ```
-look for resources with an external apiversion (not _v1_, _apps/v1_, _storage.k8s.io/v1_ or _batch/v1_ for example).
+Look for resources with an external apiversion (not _v1_, _apps/v1_, _storage.k8s.io/v1_ or _batch/v1_ for example).
 
 <Message type="note">
     It is known that cluster with many nodes and with at least one GPU node may have a lot of _nodefeatures_ objects polluting their etcd space. We are working on a long-term fix but for now manually deleting these objects and downsizing the cluster (or upgrading to a dedicated offer with a bigger etcd quota) is the best solution.