From c5c3b16e58d7187434eae9f0cbe8161e73269082 Mon Sep 17 00:00:00 2001
From: amalhotra-mdb <135728846+amalhotra-mdb@users.noreply.github.com>
Date: Tue, 18 Mar 2025 10:52:09 -0400
Subject: [PATCH] DOCSP-48393-reorder-shardingEntries-note (#672)

(cherry picked from commit d91d9a3a9b479e7c8fb35a14230d2bf327214f54)
---
 source/reference/api/start.txt | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/source/reference/api/start.txt b/source/reference/api/start.txt
index 29a4a4996..2708ade7a 100644
--- a/source/reference/api/start.txt
+++ b/source/reference/api/start.txt
@@ -192,6 +192,11 @@ Sharding Parameters
 To sync from a replica set to a sharded cluster, set the 
 ``sharding`` option to shard collections on the destination cluster.
 
+``mongosync`` throws an error if the ``sharding`` option is not set when
+syncing from a replica set to a sharded cluster. ``mongosync`` also
+throws an error if the ``sharding`` option is set with any other
+configuration.
+
 The ``sharding`` option has the following parameters:
 
 .. list-table::
@@ -240,11 +245,6 @@ The ``sharding`` option has the following parameters:
 
        For more information, see :ref:`shard-key`.
 
-``mongosync`` throws an error if the ``sharding`` option is not set when
-syncing from a replica set to a sharded cluster.  ``mongosync`` also
-throws an error if the ``sharding`` option is set with any other
-configuration.
-
 Response
 --------