Update kubernetes operations backup section

Author: bfeshti

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

@@ -8,64 +8,30 @@ For performing backups, Neo4j uses the _Admin Service_, which is only available
 For more information, see xref:kubernetes/accessing-neo4j.adoc[Accessing Neo4j].
 ====
 
-[[kubernetes-backup-modes]]
-== Backup modes
+[[kubernetes-backup-storage-options]]
+== Backup storage options
 
-Neo4j's Helm chart supports two backup modes:
+Neo4j's Helm chart supports both full and differential backups and can be configured to use cloud providers or local storage.
 
-=== Cloud provider mode
-Uses Neo4j's native cloud storage integration with direct upload to create immutable backup objects:
+=== Cloud storage
 
-* **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`
+Neo4j Helm chart uses Neo4j's native cloud storage integration with direct upload to create immutable backup objects.
+This allows you to back up your Neo4j databases directly to cloud storage without the need for persistent volumes.
+The chart can be configured to use cloud providers, such as AWS S3, Google Cloud Storage, and Azure Blob Storage, by setting the `cloudProvider` parameter to `aws`, `gcp`, or `azure` in the _backup-values.yaml_ file.
 
-=== Local mode  
-Creates local backups in `/backups` mount:
+The following features are supported:
 
-* **Requirements**: Persistent storage for large databases (configured via `tempVolume`)
-* **Configuration**: Leave `cloudProvider` empty
+* *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-cloud-native-features]]
-== Cloud-native backup features
+=== Local storage
 
-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
-
-[[kubernetes-differential-backups]]
-== Differential backups
-
-For cloud providers, differential backups eliminate the need for persistent volumes:
-
-[source, yaml, subs="attributes+,+macros"]
-----
-backup:
-  cloudProvider: "aws"
-  bucketName: "my-backups"
-  preferDiffAsParent: true
-  type: "AUTO"  # First backup will be FULL, subsequent ones DIFF
-  fallbackToFull: true  # Fallback to FULL if DIFF fails
-----
-
-**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
-
-[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
-====
+Local storage creates local backups in the `/backups` mount.
+This mount must be configured to use a persistent storage for large databases using `tempVolume`.
+The `cloudProvider` must be empty.
 
 [[kubernetes-neo4j-backup-cloud]]
 == Prepare to back up a database(s) to a cloud provider (AWS, GCP, and Azure) bucket
@@ -91,6 +57,12 @@ For more information, see link:https://min.io/docs/minio/linux/integrations/aws-
 * The latest Neo4j Helm charts.
 You can update the repository to get the latest charts using `helm repo update`.
 
+[NOTE]
+====
+When using cloud providers, differential backups do not require persistent volumes with previous backups.
+Instead, the chart will first create a full backup in the cloud storage, and then, the subsequent backups will be differential backups that reference this full backup.
+====
+
 === Create a Kubernetes secret
 
 You can create a Kubernetes secret with the credentials that can access the cloud provider bucket using one of the following options:
@@ -366,7 +338,8 @@ tempVolume:
 
 [NOTE]
 ====
-You need to create the persistent volume and persistent volume claim before installing the _neo4j-admin_ Helm chart.
+You need to create the persistent volume and persistent volume claim before installing the _neo4j-admin_ Helm chart only when using local storage.
+When using cloud providers, persistent volumes are not required for differential backups.
 For more information, see xref:kubernetes/persistent-volumes.adoc[Volume mounts and persistent volumes].
 ====
 
@@ -508,7 +481,7 @@ When configuring the _backup-values.yaml_ file, keep the “cloudProvider” fie
 
 [NOTE]
 ====
-You need to create the persistent volume and persistent volume claim before installing the _neo4j-admin_ Helm chart.
+You need to create the persistent volume and persistent volume claim before installing the _neo4j-admin_ Helm chart only when using local storage.
 For more information, see xref:kubernetes/persistent-volumes.adoc[Volume mounts and persistent volumes].
 ====
 
@@ -1081,15 +1054,17 @@ To restore the `system` database, follow the steps described in xref:kubernetes/
 ====
 
 [[kubernetes-backup-migration]]
-== Migration from traditional to cloud-native backups
+== Migrate from traditional to cloud-native backups
 
 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
+1. **Perform a final traditional backup** to ensure you have the latest data.
+For more information, see <<kubernetes-neo4j-backup-on-prem, Prepare to back up a database(s) to on-premises storage>> and <<kubernetes-neo4j-backup, Back up your databases>>.
+2. **Upload existing backups to the cloud storage bucket** if needed.
+You can use cloud provider CLI tools such as `aws s3 cp`, `gsutil cp`, or `az storage blob upload` to transfer your backup files.
+3. **Update configuration** to use cloud provider by setting the `cloudProvider` parameter.
+4. **Remove persistent volume configuration** from your _backup-values.yaml_ file.
+5. **Enable `preferDiffAsParent`** for future differential backups.
 
 .Example migration
 [source, yaml]