DOCSP-23937 Fix Role Issue on Mongosync Start Page (#287)

* DOCSP-23937 Fix Role Issue on Mongosync Start Page

* DOCSP-23937 updates for RS' feedback

Author: kanchana-mongodb

source/reference/api/start.txt

@@ -27,36 +27,18 @@ State
 To use the ``start`` endpoint, ``mongosync`` must be in the ``IDLE``
 state.
 
-User Write Blocking
-~~~~~~~~~~~~~~~~~~~
-
-.. include:: /includes/fact-write-blocking-requirement.rst
-
-To set a custom role for the ``mongosync`` user:
- 
-#. To create a custom role, use the :dbcommand:`createRole` command:
-
-   .. code-block:: javascript
-   
-      db.adminCommand( {
-         createRole: "reverseSync",
-         privileges: [ {
-             resource: { db: "", collection: "" },
-             actions: [ "setUserWriteBlockMode", "bypassWriteBlockingMode" ]
-         } ],
-         roles: []
-      } )
- 
-#. To grant the custom role to the ``mongosync`` user, use the :dbcommand:`grantRolesToUser` command:
+Permissions
+~~~~~~~~~~~
 
-   .. code-block:: javascript
+The user specified in the ``mongosync`` connection string must have the
+required permissions on the source and destination clusters. Refer to
+:ref:`c2c-permissions-and-roles` to ensure that the user has the correct
+permissions to start the synchronization.
 
-      db.adminCommand( {
-         grantRolesToUser: "mongosync-user",
-         roles: [ { role: "reverseSync", db: "admin" } ]
-      } )
+Multiple ``mongosync`` Instances
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Ensure that you use this configured ``mongosync`` user in the connection 
+Ensure that you use the configured ``mongosync`` user in the connection 
 strings for the :setting:`cluster0` or :setting:`cluster1` settings when
 you start ``mongosync``.