Minor changes (#413)

* usage.rst & asyncio_client.rst

* Update docs/api/asyncio_client.rst

Co-authored-by: Devon Campbell <devon@radworks.io>

---------

Co-authored-by: Devon Campbell <devon@radworks.io>

Author: 2 people

docs/api/asyncio_client.rst

@@ -557,8 +557,8 @@ transaction), so we have to redo all the work done.
 Generally it's recommended to not execute any long running
 code within the transaction unless absolutely necessary.
 
-Transactions allocate expensive server resources and having
-too many concurrently running long-running transactions will
+Transactions allocate expensive server resources, and having
+too many concurrent long-running transactions will
 negatively impact the performance of the DB server.
 
 To rollback a transaction that is in progress raise an exception.

docs/usage.rst

@@ -78,8 +78,8 @@ types and vice versa.  See :ref:`edgedb-python-datatypes` for details.
 Client connection pools
 -----------------------
 
-For server-type type applications that handle frequent requests and need
-the database connection for a short period time while handling a request,
+For server-type applications that handle frequent requests and need
+the database connection for a short period of time while handling a request,
 the use of a connection pool is recommended. Both :py:class:`edgedb.Client`
 and :py:class:`edgedb.AsyncIOClient` come with such a pool.