Update minio-on-premise-repository.md (#2151)

Update MinIO multi-node link label to the new naming used for MinIO
architecture used in production.

Author: eedugon

deploy-manage/tools/snapshot-and-restore/minio-on-premise-repository.md

@@ -28,7 +28,7 @@ For installation instructions, refer to the official [MinIO documentation](https
 
 The performance and reliability of MinIO depend on its configuration and the underlying infrastructure. Consider the following best practices:
 
-* For production use, deploy MinIO in [distributed mode](https://min.io/docs/minio/linux/operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.html#minio-mnmd).
+* For production use, deploy MinIO in a [Multi-Node Multi-Drive](https://min.io/docs/minio/linux/operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.html#minio-mnmd) configuration.
 * Use a single MinIO endpoint with the ECE installation, to simplify repository configuration.
 * Secure access to the MinIO endpoint with TLS.
 
@@ -48,7 +48,9 @@ Use the [MinIO Quickstart Guide](https://charts.min.io/) or the [container deplo
 
 ### Production environments
 
-Set up MinIO in distributed mode across multiple nodes and drives. You can use Docker Compose, Kubernetes, or another orchestration tool of your choice.
+Set up MinIO across multiple nodes and drives to ensure high availability, performance, and scalability, following the recommendations in the [MinIO documentation](https://min.io/docs/minio/linux/operations/install-deploy-manage/deploy-minio-multi-node-multi-drive.html).
+
+You can use Docker Compose, Kubernetes, or another orchestration tool of your choice.
 
 ## Create the S3 bucket [ece-minio-create-s3-bucket]