CDRIVER-1979 simpler RST markup

Now :symbol:`function()` and :symbol:`function` work the same, but let
you choose whether to include parentheses.

Author: ajdavis

doc/application-performance-monitoring.rst

@@ -8,7 +8,7 @@ The MongoDB C Driver allows you to monitor all the MongoDB operations the driver
 * `Command Monitoring <https://github.com/mongodb/specifications/blob/master/source/command-monitoring/command-monitoring.rst>`_: events related to all application operations.
 * `SDAM Monitoring <https://github.com/mongodb/specifications/blob/master/source/server-discovery-and-monitoring/server-discovery-and-monitoring-monitoring.rst>`_: events related to the driver's Server Discovery And Monitoring logic.
 
-To receive notifications, create a ``mongoc_apm_callbacks_t`` with :symbol:`mongoc_apm_callbacks_new <mongoc_apm_callbacks_new>`, set callbacks on it, then pass it to :symbol:`mongoc_client_set_apm_callbacks <mongoc_client_set_apm_callbacks>` or :symbol:`mongoc_client_pool_set_apm_callbacks <mongoc_client_pool_set_apm_callbacks>`.
+To receive notifications, create a ``mongoc_apm_callbacks_t`` with :symbol:`mongoc_apm_callbacks_new`, set callbacks on it, then pass it to :symbol:`mongoc_client_set_apm_callbacks` or :symbol:`mongoc_client_pool_set_apm_callbacks`.
 
 Command-Monitoring Example
 --------------------------

doc/bulk.rst

@@ -8,7 +8,7 @@ This tutorial explains how to take advantage of MongoDB C driver bulk write oper
 Bulk Insert
 -----------
 
-First we need to fetch a bulk operation handle from the :symbol:`mongoc_collection_t <mongoc_collection_t>`. This can be performed in either ordered or unordered mode. Unordered mode allows for greater parallelization when working with sharded clusters.
+First we need to fetch a bulk operation handle from the :symbol:`mongoc_collection_t`. This can be performed in either ordered or unordered mode. Unordered mode allows for greater parallelization when working with sharded clusters.
 
 .. code-block:: c
 
@@ -17,13 +17,13 @@ First we need to fetch a bulk operation handle from the :symbol:`mongoc_collecti
 
 We can now start inserting documents to the bulk operation. These will be buffered until we execute the operation.
 
-The bulk operation will coalesce insertions as a single batch for each consecutive call to :symbol:`mongoc_bulk_operation_insert() <mongoc_bulk_operation_insert>`. This creates a pipelined effect when possible.
+The bulk operation will coalesce insertions as a single batch for each consecutive call to :symbol:`mongoc_bulk_operation_insert()`. This creates a pipelined effect when possible.
 
 .. tip::
 
   The bulk operation API will automatically handle MongoDB servers < 2.6 by speaking the old wire protocol. However, some performance degradation may occur.
 
-To execute the bulk operation and receive the result we call :symbol:`mongoc_bulk_operation_execute() <mongoc_bulk_operation_execute>`.
+To execute the bulk operation and receive the result we call :symbol:`mongoc_bulk_operation_execute()`.
 
 .. literalinclude:: ../examples/bulk/bulk1.c
    :language: c
@@ -48,7 +48,7 @@ MongoDB C driver also supports executing mixed bulk write operations. A batch of
 
 .. tip::
 
-  Though the following API will work with all versions of MongoDB, it is designed to be used with MongoDB versions >= 2.6. Much better bulk insert performance can be achieved with older versions of MongoDB through the deprecated :symbol:`mongoc_collection_insert_bulk() <mongoc_collection_insert_bulk>` method.
+  Though the following API will work with all versions of MongoDB, it is designed to be used with MongoDB versions >= 2.6. Much better bulk insert performance can be achieved with older versions of MongoDB through the deprecated :symbol:`mongoc_collection_insert_bulk()` method.
 
 Ordered Bulk Write Operations
 -----------------------------
@@ -150,7 +150,7 @@ The :symbol:`bson_error_t <errors>` domain is ``MONGOC_ERROR_COMMAND``.
 Bulk Operation Write Concerns
 -----------------------------
 
-By default bulk operations are executed with the :symbol:`write_concern <mongoc_write_concern_t>` of the collection they are executed against. A custom write concern can be passed to the :symbol:`mongoc_collection_create_bulk_operation() <mongoc_collection_create_bulk_operation>` method. Write concern errors (e.g. wtimeout) will be reported after all operations are attempted, regardless of execution order.
+By default bulk operations are executed with the :symbol:`write_concern <mongoc_write_concern_t>` of the collection they are executed against. A custom write concern can be passed to the :symbol:`mongoc_collection_create_bulk_operation()` method. Write concern errors (e.g. wtimeout) will be reported after all operations are attempted, regardless of execution order.
 
 .. literalinclude:: ../examples/bulk/bulk4.c
    :language: c

doc/cursors.rst

@@ -39,14 +39,14 @@ While iterating cursors, you should check to see if an error has occurred. See t
 Destroying Server-Side Cursors
 ------------------------------
 
-The MongoDB C driver will automatically destroy a server-side cursor when :symbol:`mongoc_cursor_destroy() <mongoc_cursor_destroy>` is called. Failure to call this function when done with a cursor will leak memory client side as well as consume extra memory server side. If the cursor was configured to never timeout, it will become a memory leak on the server.
+The MongoDB C driver will automatically destroy a server-side cursor when :symbol:`mongoc_cursor_destroy()` is called. Failure to call this function when done with a cursor will leak memory client side as well as consume extra memory server side. If the cursor was configured to never timeout, it will become a memory leak on the server.
 
 .. _cursors_tailable:
 
 Tailable Cursors
 ----------------
 
-Tailable cursors are cursors that remain open even after they've returned a final result. This way, if more documents are added to a collection (i.e., to the cursor's result set), then you can continue to call :symbol:`mongoc_cursor_next() <mongoc_cursor_next>` to retrieve those additional results.
+Tailable cursors are cursors that remain open even after they've returned a final result. This way, if more documents are added to a collection (i.e., to the cursor's result set), then you can continue to call :symbol:`mongoc_cursor_next()` to retrieve those additional results.
 
 Here's a complete test case that demonstrates the use of tailable cursors.
 
@@ -68,5 +68,5 @@ Let's compile and run this example against a replica set to see updates as they
 
 The line of output is a sample from performing ``db.test.insert({})`` from the mongo shell on the given replicaSet.
 
-See also :symbol:`mongoc_cursor_set_max_await_time_ms <mongoc_cursor_set_max_await_time_ms>`.
+See also :symbol:`mongoc_cursor_set_max_await_time_ms`.