Remove AWS from the MinIO (#1229) (#1235)

Cherry-picked from #1229

Author: renetapopova

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

@@ -29,7 +29,7 @@ Before you can back up a database and upload it to your bucket, verify that you
 ** For more information on setting up an Azure storage account with workload identity, link:https://learn.microsoft.com/en-us/azure/aks/workload-identity-overview?tabs=go[Microsoft Azure -> Use Microsoft Entra Workload ID with Azure Kubernetes Service (AKS)]
 * A Kubernetes cluster running on one of the cloud providers with the Neo4j Helm chart installed.
 For more information, see xref:kubernetes/quickstart-standalone/index.adoc[Quickstart: Deploy a standalone instance] or xref:kubernetes/quickstart-cluster/index.adoc[Quickstart: Deploy a cluster].
-* MinIO server (an AWS S3-compatible object storage API) if you want to push your backups to a MinIO bucket on AWS.
+* MinIO server (an AWS S3-compatible object storage API) if you want to push your backups to a MinIO bucket.
 Only non-TLS/SSL endpoints are supported.
 For more information, see link:https://min.io/docs/minio/linux/integrations/aws-cli-with-minio.html[MinIO official documentation].
 * The latest Neo4j Helm charts.
@@ -295,7 +295,7 @@ For more information, see xref:kubernetes/persistent-volumes.adoc[Volume mounts
 _This feature is available from Neo4j 5.14._
 
 MinIO is an AWS S3-compatible object storage API.
-You can specify the `minioEndpoint` parameter in the _backup-values.yaml_ file to push your backups to your MinIO bucket on AWS.
+You can specify the `minioEndpoint` parameter in the _backup-values.yaml_ file to push your backups to your MinIO bucket.
 This endpoint must be a s3 API endpoint or else the backup Helm chart will fail.
 Only non-TLS/SSL endpoints are supported.
 For example: