Apply suggestions from code review

Co-authored-by: Jessica <[email protected]>

Author: bene2k1

containers/kubernetes/troubleshooting/configuring-sql-storage-backend-helm.mdx

@@ -19,7 +19,7 @@ When deploying large Helm releases on Scaleway Kapsule Kubernetes, you might enc
 rpc error: code = ResourceExhausted desc = etcd quota exceeded: size 55000000/55000000, burst 424242/100000000
 ```
 
-This happens because Helm stores release information in Kubernetes **Secrets** or **ConfigMaps**, which are limited to 1MB due to **etcd** storage constraints.
+This happens because Helm stores release information in Kubernetes **Secrets** or **ConfigMaps**, which are limited to 1 MB due to **etcd** storage constraints.
 
 To resolve this issue, you can configure Helm to use an SQL storage backend such as **PostgreSQL**, bypassing the etcd size limitations and enabling larger Helm releases.
 
@@ -91,7 +91,7 @@ Helm does not automatically migrate releases between storage backends. Follow th
 
 ### Backup existing releases
 
-- Run the following command to backup your existing releases:
+- Run the following command to back up your existing releases:
     ```bash
     kubectl get secrets --all-namespaces -l "owner=helm" -o yaml > helm-backup.yaml
     ```