fix

Author: ajdavis

doc/mongoc_client_set_write_concern.page

@@ -15,7 +15,8 @@
     <synopsis><code mime="text/x-csrc"><![CDATA[void
 mongoc_client_set_write_concern (mongoc_client_t              *client,
                                  const mongoc_write_concern_t *write_concern);]]></code></synopsis>
-    <p>Sets the default write concern for the client. This only affects future operations, collections, and databases inheriting from <code>client</code>.</p>
+    <p>Sets the write concern for the client. This only affects future operations, collections, and databases inheriting from <code>client</code>.</p>
+    <p>The default write concern is MONGOC_WRITE_CONCERN_W_DEFAULT: the driver blocks awaiting basic acknowledgment of write operations from MongoDB. This is the correct write concern for the great majority of applications.</p>
   </section>
 
   <section id="parameters">

doc/mongoc_collection_create_bulk_operation.page

@@ -40,7 +40,7 @@ mongoc_collection_create_bulk_operation (
     <p>After calling <link xref="mongoc_bulk_operation_execute">mongoc_bulk_operation_execute()</link> the commands will be executed in as large as batches as reasonable by the client.</p>
     <p>If <code>ordered</code> is true, then processing will stop at the first error.</p>
     <p>If <code>ordered</code> is not true, then the bulk operation will attempt to continue processing even after the first failure.</p>
-    <p><code>write_concern</code> should contain the write concern you wish to have applied to all operations within the bulk operation.</p>
+    <p><code>write_concern</code> contains the write concern for all operations in the bulk operation. If NULL, the collection's write concern is used. The global default is acknowledged writes: MONGOC_WRITE_CONCERN_W_DEFAULT.</p>
   </section>
 
   <section id="errors">

doc/mongoc_collection_set_write_concern.page

@@ -28,7 +28,8 @@ mongoc_collection_set_write_concern (mongoc_collection_t          *collection,
 
   <section id="description">
     <title>Description</title>
-    <p>Sets the default write concern to use for operations on <code>collection</code> not specifying a write concern.</p>
+    <p>Sets the write concern to use for operations on <code>collection</code>.</p>
+    <p>The default write concern is MONGOC_WRITE_CONCERN_W_DEFAULT: the driver blocks awaiting basic acknowledgment of write operations from MongoDB. This is the correct write concern for the great majority of applications.</p>
   </section>
 
 </page>

doc/mongoc_database_set_write_concern.page

@@ -19,7 +19,8 @@
 mongoc_database_set_write_concern (mongoc_database_t            *database,
                                    const mongoc_write_concern_t *write_concern);
 ]]></code></synopsis>
-    <p>This function sets the default write concern to use on operations performed with <code>database</code>. Collections created with <link xref="mongoc_database_get_collection">mongoc_database_get_collection()</link> after this call will inherit this write concern.</p>
+    <p>This function sets the write concern to use on operations performed with <code>database</code>. Collections created with <link xref="mongoc_database_get_collection">mongoc_database_get_collection()</link> after this call will inherit this write concern.</p>
+    <p>The default write concern is MONGOC_WRITE_CONCERN_W_DEFAULT: the driver blocks awaiting basic acknowledgment of write operations from MongoDB. This is the correct write concern for the great majority of applications.</p>
   </section>
 
   <section id="parameters">