further editorial updates

Author: renetapopova

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

@@ -56,9 +56,9 @@ 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 is required.
+. First backup creates a FULL backup in cloud storage.
+. Subsequent backups create DIFF backups that reference the cloud-stored FULL backup.
+. No local storage of previous backups is required.
 
 [NOTE]
 ====
@@ -478,9 +478,7 @@ backup:
 
 === S3 CA certificate setup
 
-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
+For S3 endpoints with custom CA certificates, use a Kubernetes secret to manage the CA certificate:
 
 . Create the CA certificate secret:
 +
@@ -1022,12 +1020,7 @@ cypher-shell -u neo4j -p <password> -d system
 ----
 DROP DATABASE neo4j;
 ----
-. Exit the Cypher Shell command-line console:
-+
-[source, shell, role='noheader']
-----
-:exit;
-----
+. Exit the Cypher Shell command-line console by typing `:exit;`.
 
 === Restore the database backup
 
@@ -1085,7 +1078,7 @@ To restore the `system` database, follow the steps described in xref:kubernetes/
 [[kubernetes-backup-migration]]
 == Migration from traditional to cloud-native backups
 
-To migrate from persistent volume-based backups to cloud-native:
+To migrate from persistent volume-based backups to cloud-native backups, you need to follow these steps:
 
 . Perform final traditional backup.
 . Upload existing backups to cloud storage (if needed).