From 032ec7158b32249e87fac8f0ceafca3e6206c2c4 Mon Sep 17 00:00:00 2001
From: Naomi Pentrel <5212232+npentrel@users.noreply.github.com>
Date: Mon, 11 Oct 2021 15:00:53 +0200
Subject: [PATCH] DOCS-14469: Address rename behaviour

---
 source/reference/method/db.collection.renameCollection.txt | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/source/reference/method/db.collection.renameCollection.txt b/source/reference/method/db.collection.renameCollection.txt
index fa85443e91b..4b740850396 100644
--- a/source/reference/method/db.collection.renameCollection.txt
+++ b/source/reference/method/db.collection.renameCollection.txt
@@ -68,7 +68,7 @@ warnings and messages.
    :dbcommand:`renameCollection` command create an
    :ref:`change-event-invalidate` for any existing
    :doc:`/changeStreams` opened on the source or target collection.
-   
+
 - The method has the following limitations:
 
   - :method:`db.collection.renameCollection()` cannot move a collection
@@ -83,6 +83,9 @@ warnings and messages.
   - :method:`db.collection.renameCollection()` is not supported on
     :term:`time series collections <time series collection>`.
 
+  - You cannot rename a collection to itself. If you try to rename a
+    collection to itself an ``IllegalOperation`` error is thrown.
+
 Resource Locking in Sharded Clusters
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~