DOCS-15696 remove refs to moveChunk-directory (#2048)

Author: jmd-mongo

source/core/sharding-balancer-administration.txt

@@ -150,10 +150,6 @@ All range migrations use the following procedure:
       without waiting for the current migration process to finish this
       deletion step. See :ref:`chunk-migration-queuing`.
 
-   .. seealso::
-   
-      :ref:`moveChunk-directory`
-
 .. seealso::
 
    :serverstatus:`shardingStatistics.countDonorMoveChunkLockTimeout`

source/core/sharding-data-partitioning.txt

@@ -196,18 +196,9 @@ leads to jumbo chunks.
 For more information, see:
 
 - :ref:`change-a-shard-key`
-
-- :doc:`/tutorial/clear-jumbo-flag`
-
+- :ref:`<clear-jumbo-flag>`
 - :ref:`migration-chunk-size-limit`
 
-.. _moveChunk-directory:
-
-``moveChunk`` directory
------------------------
-
-By default, :setting:`sharding.archiveMovedChunks` is disabled.
-
 .. toctree::
    :titlesonly: 
    :hidden: 

source/includes/fact-adding-shards-changes-cluster-balance.rst

@@ -3,5 +3,3 @@ When you add a shard to a sharded cluster, you affect the balance of
 collections. The balancer will begin migrating chunks so that the
 cluster will achieve balance. See :ref:`sharding-internals-balancing` for
 more information.
-
-.. include:: /includes/fact-archiveMovedChunks.rst

source/includes/fact-archiveMovedChunks.rst

@@ -1,3 +1,5 @@
+.. _clear-jumbo-flag:
+
 ====================
 Clear ``jumbo`` Flag
 ====================