editorial updates

Author: renetapopova

modules/ROOT/pages/kubernetes/operations/backup-restore.adoc

@@ -14,28 +14,30 @@ For more information, see xref:kubernetes/accessing-neo4j.adoc[Accessing Neo4j].
 Neo4j's Helm chart supports two backup modes:
 
 === Cloud provider mode
-Uses Neo4j's native cloud storage integration with direct upload to create immutable backup objects:
 
-* **Supported providers**: AWS S3, Google Cloud Storage, Azure Blob Storage
-* **Benefits**: No persistent volume requirements, supports differential backups, immutable backup objects
-* **Configuration**: Set `cloudProvider` to `aws`, `gcp`, or `azure`
+Cloud provider mode uses Neo4j's native cloud storage integration with direct upload to create immutable backup objects.
 
-=== Local mode  
-Creates local backups in `/backups` mount:
+* **Supported providers**: AWS S3, Google Cloud Storage, and Azure Blob Storage.
+* **Benefits**: No persistent volume requirements. Supports differential backups and immutable backup objects.
+* **Configuration**: Set `cloudProvider` to `aws`, `gcp`, or `azure`.
 
-* **Requirements**: Persistent storage for large databases (configured via `tempVolume`)
-* **Configuration**: Leave `cloudProvider` empty
+=== Local mode
+
+Local mode creates local backups in `/backups` mount.
+
+* **Requirements**: Persistent storage for large databases (configured via `tempVolume`).
+* **Configuration**: Leave `cloudProvider` empty.
 
 [[kubernetes-cloud-native-features]]
 == Cloud-native backup features
 
 When using cloud providers, Neo4j's native backup provides:
 
-* **Direct cloud storage upload** - No intermediate local storage required
-* **Differential backup chains** with `preferDiffAsParent: true`
-* **Immutable backup objects** in cloud storage
-* **Support for S3-compatible endpoints**
-* **Enhanced S3 configuration** including custom CA certificates and endpoint settings
+* **Direct cloud storage upload** - No intermediate local storage required.
+* **Differential backup chains** with `preferDiffAsParent: true`.
+* **Immutable backup objects** in cloud storage.
+* **Support for S3-compatible endpoints**.
+* **Enhanced S3 configuration** including custom CA certificates and endpoint settings.
 
 [[kubernetes-differential-backups]]
 == Differential backups
@@ -54,17 +56,17 @@ backup:
 
 **How it works:**
 
-1. First backup creates a FULL backup in cloud storage
-2. Subsequent backups create DIFF backups that reference the cloud-stored FULL backup
-3. No local storage of previous backups required
+1. First backup creates a FULL backup in cloud storage.
+2. Subsequent backups create DIFF backups that reference the cloud-stored FULL backup.
+3. No local storage of previous backups is required.
 
 [NOTE]
 ====
 **`preferDiffAsParent` is fully supported and eliminates the need for persistent volumes!**
 
-* **Helm Value**: `backup.preferDiffAsParent: true`
-* **Cloud-Native**: DIFF backups reference cloud-stored FULL backups directly
-* **No PV Required**: Previous backups don't need to be stored locally
+* **Helm Value**: `backup.preferDiffAsParent: true`.
+* **Cloud-Native**: DIFF backups reference cloud-stored FULL backups directly.
+* **No PV Required**: Previous backups don't need to be stored locally.
 ====
 
 [[kubernetes-neo4j-backup-cloud]]
@@ -476,18 +478,18 @@ backup:
 
 === S3 CA certificate setup
 
-For S3 endpoints with custom CA certificates:
+For S3 endpoints with custom CA certificates, you can either provide the CA certificate directly in the _backup-values.yaml_ file or use a Kubernetes secret to manage the CA certificate.
 
 ==== Using Kubernetes secrets
 
-1. **Create the CA certificate secret:**
+. Create the CA certificate secret:
 +
 [source, bash]
 ----
 kubectl create secret generic s3-ca-cert --from-file=ca.crt=/path/to/your/ca.crt
 ----
 
-2. **Configure the backup job:**
+. Configure the backup job:
 +
 [source, yaml]
 ----
@@ -1085,11 +1087,11 @@ To restore the `system` database, follow the steps described in xref:kubernetes/
 
 To migrate from persistent volume-based backups to cloud-native:
 
-1. **Perform final traditional backup**
-2. **Upload existing backups to cloud storage** (if needed)
-3. **Update configuration** to use cloud provider
-4. **Remove persistent volume configuration**
-5. **Enable `preferDiffAsParent`** for future differential backups
+. Perform final traditional backup.
+. Upload existing backups to cloud storage (if needed).
+. Update configuration to use cloud provider.
+. Remove persistent volume configuration.
+. Enable `preferDiffAsParent` for future differential backups.
 
 .Example migration
 [source, yaml]