Apply suggestions from code review

Co-authored-by: Andrea Longo <feorlen@users.noreply.github.com>
Co-authored-by: Allan Roger Reid <allanrogerreid@gmail.com>

Author: 3 people

source/operations/install-deploy-manage/deploy-minio-tenant-helm.rst

@@ -105,7 +105,7 @@ It provides a baseline from which you can modify and tailor the Tenant to your r
 
       curl -sLo values.yaml https://raw.githubusercontent.com/minio/operator/master/helm/tenant/values.yaml
 
-   Open the ``values.yaml`` object in your preferred text edit.
+   Open the ``values.yaml`` object in your preferred text editor.
 
 #. Configure the Tenant topology
 
@@ -144,7 +144,7 @@ It provides a baseline from which you can modify and tailor the Tenant to your r
 
 #. Configure Network Encryption
 
-   The MinIO Tenant CRD provides the following fields from which you can configure tenant TLS network encryption:
+   The MinIO Tenant CRD provides the following fields with which you can configure tenant TLS network encryption:
 
    .. list-table::
       :header-rows: 1
@@ -175,7 +175,7 @@ It provides a baseline from which you can modify and tailor the Tenant to your r
 
    The YAML includes an object ``kind: Secret`` with ``metadata.name: storage-configuration`` that sets the root username, password, erasure parity settings, and enables Tenant Console.
 
-   Modify this as-needed to reflect your Tenant requirements.
+   Modify this as needed to reflect your Tenant requirements.
 
 #. Deploy the Tenant
 
@@ -188,7 +188,7 @@ It provides a baseline from which you can modify and tailor the Tenant to your r
         --namespace minio-tenant-1 \
         --create-namespace \
         --values values.yaml \
-        tenant minio/tenant
+        tenant minio-operator/tenant
 
    You can monitor the progress using the following command:
 
@@ -247,7 +247,7 @@ This method may support easier pre-configuration of the Tenant compared to the :
    Each chart contains a ``values.yaml`` file you can customize to suit your needs.
    For details on the options available in the MinIO Tenant ``values.yaml``, see :ref:`minio-tenant-chart-values`.
 
-   Open the ``values.yaml`` object in your preferred text edit.
+   Open the ``values.yaml`` object in your preferred text editor.
 
 #. Configure the Tenant topology
 

source/operations/install-deploy-manage/upgrade-minio-operator-4.5.7-earlier.rst

@@ -11,7 +11,7 @@ Upgrade Legacy MinIO Operators
    :depth: 1
 
 
-MinIO spuports the following upgrade paths for older versions of the MinIO Operator:
+MinIO supports the following upgrade paths for older versions of the MinIO Operator:
 
 .. list-table::
    :header-rows: 1

source/operations/install-deploy-manage/upgrade-minio-operator.rst

@@ -119,7 +119,7 @@ Upgrade Operator to |operator-version-stable|
 
          MinIO does not remove the old Console services, pods, or deployments as per Kubernetes standard procedure.
          You can remove these resources at your own discretion.
-         MinIO is no longer developing nor supporting the Console, and as of such advises against long-term reliance on the Console for Tenant management.
+         MinIO is no longer developing nor supporting the Operator Console, and as of such advises against long-term reliance on this Console for Tenant management.
 
          You can continue to use Kustomize to deploy and manage MinIO Tenants.