Update documentation

Author: joowani

docs/client.rst

@@ -42,4 +42,4 @@ and used:
     result = db.aql.execute('FOR s IN students RETURN s')
     print([student['name'] for student in result])
 
-Pretty simple right? Read the rest of the documentation to discover much more!
+Read the rest of the documentation to discover much more!

docs/database.rst

@@ -5,11 +5,11 @@ Databases
 
 A single ArangoDB instance can house multiple databases, which in turn contain
 their own set of worker processes,  :ref:`collections <collection-page>`, and
-:ref:`graphs <graph-page>`. There must always be a default database named
-``_system``. This database cannot be dropped, can only be accessed with root
+:ref:`graphs <graph-page>`. There is always a default database named ``_system``.
+This default database cannot be dropped, can only be accessed with root
 privileges, and provides operations for managing other user-defined databases.
 
-Here is an example showing how databases can be managed with different users:
+Here is an example showing how databases can be managed with multiple users:
 
 .. code-block:: python
 
@@ -41,7 +41,7 @@ Here is an example showing how databases can be managed with different users:
 
     # To switch to a different user, simply create a new database object with
     # the credentials of the desired user (which in this case would be jane's)
-    db = client.database('another_database', username='jane', password='bar')
+    db = client.database('another_database', username='jane', password='foo')
 
     # Delete an existing database as root
     client.delete_database('another_database')

docs/document.rst

@@ -5,14 +5,14 @@ Documents
 
 **Documents** in python-arango are Python dictionaries. They can be nested to
 an arbitrary depth and contain lists. Each document must have the ``"_key"``
-field, whose value identifies the document uniquely within a given collection.
-There is also the ``"_id"`` field, whose value identifies the document uniquely
-across *all* collections within a given database.
+field, whose value identifies the document uniquely within a collection. There
+is also the ``"_id"`` field, whose value identifies the document uniquely across
+*all* collections within a database.
 
 ArangoDB supports MVCC (Multiple Version Concurrency Control) and is capable
-of storing each document in multiple revisions. The revision of a document can
-be distinguished by the value of the ``"_rev"`` field. For more information on
-document basics and terminologies visit this
+of storing each document in multiple revisions. The revision of a document is
+distinguished by the value of the ``"_rev"`` field. For more information on
+documents and their associated terminologies visit this
 `page <https://docs.arangodb.com/HTTP/Document/AddressAndEtag.html>`__.
 
 Here is an example of a valid document:
@@ -28,7 +28,7 @@ Here is an example of a valid document:
         'address': {
             'city': 'Gotham',
             'zip': 'M1NS93',
-            'street' : '300 Beverly St.',
+            'street' : '300 Beverly St.'
         },
         'courses': ['CSC101', 'STA101']
     }
@@ -37,7 +37,7 @@ Here is an example of a valid document:
 
 **Edge documents** or **edges** are similar to documents but with additional
 required fields ``"_from"`` and ``"_to"``. The values of these fields are the
-values of the ``"_id"`` field in the "from" and "to" vertex documents (see
+values of the ``"_id"`` field of the "from" and "to" vertex documents (see
 :ref:`graphs <graph-page>` for more details). Edge documents are contained in
 :ref:`edge collections <edge-collections>`.
 
@@ -52,7 +52,7 @@ Here is an example of a valid edge document:
         '_from': 'students/john',
         '_to': 'students/jane',
         'friends': True,
-        'closeness': 10
+        'family': False
     }
 
 

docs/errors.rst

@@ -6,7 +6,7 @@ which lightly wraps around the HTTP error responses returned from ArangoDB.
 The majority of the error messages in the exceptions raised by python-arango
 come directly from the server.
 
-Here is an example showing how a python-arango exception can be caught:
+Here is an example showing how a python-arango exception can be handled:
 
 .. code-block:: python
 

docs/graph.rst

@@ -3,7 +3,7 @@
 Graphs
 ------
 
-An **graph** consists of **vertices** and **edges**. Edges are stored as
+A **graph** consists of **vertices** and **edges**. Edges are stored as
 documents in :ref:`edge collections <edge-collections>`, whereas vertices
 are stored as documents in :ref:`vertex collections <vertex-collections>`
 (edges can be vertices also). The combination of edge and vertex collections
@@ -144,7 +144,7 @@ Refer to :ref:`Graph` and :ref:`EdgeCollection` classes for more details.
 Graph Traversals
 ================
 
-**Graph traversals** can executed via the :func:`~arango.graph.Graph.traverse`
+**Graph traversals** are executed via the :func:`~arango.graph.Graph.traverse`
 method. A traversal can span across multiple vertex collections and walk over
 the documents in a variety of ways.
 

docs/logging.rst

@@ -3,7 +3,7 @@
 Logging
 -------
 
-By default, :class:`arango.ArangoClient` logs API call history using the
+By default, :class:`arango.ArangoClient` records API call history using the
 ``arango`` logger at ``logging.DEBUG`` level.
 
 Here is an example showing how the logger can be enabled and customized:
@@ -19,7 +19,7 @@ Here is an example showing how the logger can be enabled and customized:
     # Set the logging level
     logger.setLevel(logging.DEBUG)
 
-    # Attach a custom handler
+    # Attach a handler
     handler = logging.StreamHandler()
     formatter = logging.Formatter('[%(levelname)s] %(message)s')
     handler.setFormatter(formatter)