diff --git a/source/extra/examples/LifecycleManagementUser.json b/source/extra/examples/LifecycleManagementUser.json
index 4b091602..b40caacc 100644
--- a/source/extra/examples/LifecycleManagementUser.json
+++ b/source/extra/examples/LifecycleManagementUser.json
@@ -24,4 +24,4 @@
             "Sid": ""
       }
    ]
-}
\ No newline at end of file
+}
diff --git a/source/reference/minio-mc/mc-ilm-tier.rst b/source/reference/minio-mc/mc-ilm-tier.rst
index 9d1660c7..39e742f7 100644
--- a/source/reference/minio-mc/mc-ilm-tier.rst
+++ b/source/reference/minio-mc/mc-ilm-tier.rst
@@ -81,7 +81,7 @@ To create tiers for object transition, MinIO requires the following administrati
 - :policy-action:`admin:SetTier`
 - :policy-action:`admin:ListTier`
 
-For example, the following policy provides permission for configuring object transition lifecycle management rules on any bucket in the cluster:.
+For example, the following policy provides sufficient permissions for configuring object transition lifecycle management rules on any bucket in the cluster:
 
 .. literalinclude:: /extra/examples/LifecycleManagementAdmin.json
    :language: json
@@ -93,7 +93,7 @@ Transition Permissions
 Object transition lifecycle management rules require additional permissions on the remote storage tier. 
 Specifically, MinIO requires the remote tier credentials provide read, write, list, and delete permissions.
 
-For example, if the remote storage tier implements AWS IAM policy-based access control, the following policy provides the necessary permission for transitioning objects into and out of the remote tier:
+For example, if the remote storage tier implements AWS IAM policy-based access control, the following policy provides the necessary permissions for transitioning objects into and out of the remote tier:
 
 .. literalinclude:: /extra/examples/LifecycleManagementUser.json
    :language: json
@@ -101,6 +101,14 @@ For example, if the remote storage tier implements AWS IAM policy-based access c
 
 Modify the ``Resource`` for the bucket into which MinIO tiers objects.
 
+.. admonition:: Avoid enabling versioning in the remote tier
+   :class: important
+
+   MinIO strongly recommends against enabling bucket versioning for remote tiers.
+   If the remote tier bucket is versioned, each source object version is transitioned to a *unique object* in the remote tier.
+   
+   If your environment requires versioning for the remote tier, you must also allow the ``s3:DeleteObjectVersion`` permission.
+
 Defer to the documentation for the supported tiering targets for more complete information on configuring users and permissions to support MinIO tiering:
 
 - :aws-docs:`Amazon S3 Permissions <service-authorization/latest/reference/list_amazons3.html#amazons3-actions-as-permissions>`
@@ -117,4 +125,4 @@ Defer to the documentation for the supported tiering targets for more complete i
    /reference/minio-mc/mc-ilm-tier-info
    /reference/minio-mc/mc-ilm-tier-ls
    /reference/minio-mc/mc-ilm-tier-rm
-   /reference/minio-mc/mc-ilm-tier-update
\ No newline at end of file
+   /reference/minio-mc/mc-ilm-tier-update