DOCSP-14153: address feedback on find usage example (#138)

Author: Chris Cho

source/code-snippets/usage-examples/find.js

@@ -30,6 +30,7 @@ async function run() {
       console.log("No documents found!");
     }
 
+    // replace console.dir with your callback to access individual elements
     await cursor.forEach(console.dir);
   } finally {
     await client.close();

source/fundamentals/crud/read-operations/cursor.txt

@@ -29,6 +29,8 @@ and :doc:`Collection.watch() </usage-examples/changeStream>` use
 cursors internally, and return the results of the operations instead of
 a cursor.
 
+.. _cursor-methods:
+
 Cursor Paradigms
 ----------------
 
@@ -57,7 +59,7 @@ pulling all matching documents into a collection in process memory.
    When you reach the last result through iteration or through an at-once
    fetch, the cursor is exhausted which means it ceases to respond to methods
    that access the results.
-   
+
 For Each Functional Iteration
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 

source/usage-examples/find.txt

@@ -22,11 +22,14 @@ objects. See :node-api:`collection.find() <Collection.html#find>` for more
 information on the parameters you can pass to the method.
 
 The ``find()`` method returns a :node-api:`Cursor <Cursor.html>` that
-manages the results of your query. Iterate through the
-:doc:`cursor </fundamentals/crud/read-operations/cursor>` using cursor
-methods like ``next()``, ``toArray()``, or ``forEach()`` to
-fetch and work with the returned documents. If no documents match the
-query, ``find()`` returns an empty cursor.
+manages the results of your query. You can iterate through the matching
+documents using one of the following :ref:`cursor methods <cursor-methods>`:
+
+- ``next()``
+- ``toArray()``
+- ``forEach()``
+
+If no documents match the query, ``find()`` returns an empty cursor.
 
 Example
 -------