DOCS-15470 add can write v1.0 (#62)

* DOCS-15470 add canWrite

* Fix section order

* Review feedback

Author: Dave Cuthbert

source/includes/api/responses/progress.json

@@ -3,6 +3,7 @@
       {
          "state":"RUNNING",
          "canCommit":true,
+         "canWrite":false,
          "info":"change event application",
          "lagTimeSeconds":0,
          "collectionCopy":

source/includes/api/tables/progress-response.rst

@@ -1,7 +1,7 @@
 .. list-table::
    :header-rows: 1
    :stub-columns: 1
-   :widths: 20 14 66
+   :widths: 20 20 60
 
    * - Field
      - Type
@@ -18,6 +18,12 @@
        request will succeed. This also means that the initial sync has
        completed and is applying change events.
 
+   * - ``canWrite``
+     - boolean
+     - If ``true``, indicates that it is possible to write to the
+       destination cluster. Index validation continues until the 
+       :ref:`commit <c2c-api-commit>` is complete.
+
    * - ``info``
      - string
      - Provides extra information on the synchronization progress.

source/reference/api/progress.txt

@@ -32,6 +32,18 @@ All response fields are wrapped in a top-level ``progress`` object.
 
 .. include:: /includes/api/tables/progress-response.rst
 
+Behavior
+--------
+
+- When ``mongosync`` is in the ``IDLE`` state, all output
+  fields except ``state`` and ``canCommit`` are ``null``.
+  
+- When ``mongosync`` is in the ``PAUSED`` state, the
+  ``lagTimeSeconds`` field is ``null``.
+
+- The endpoint does not auto-refresh. To get updated status, call the
+  ``progress`` endpoint again.
+
 Example
 -------
 
@@ -50,15 +62,3 @@ Response
    :language: json
    :copyable: false
 
-Behavior
---------
-
-- When ``mongosync`` is in the ``IDLE`` state, all output
-  fields except ``state`` and ``canCommit`` are ``null``.
-  
-- When ``mongosync`` is in the ``PAUSED`` state, the
-  ``lagTimeSeconds`` field is ``null``.
-
-- The endpoint does not auto-refresh. To get updated status, call the
-  ``progress`` endpoint again.
-