diff --git a/docs/source/api-vault-query.rst b/docs/source/api-vault-query.rst
index b0f295268e..1adb4631b9 100644
--- a/docs/source/api-vault-query.rst
+++ b/docs/source/api-vault-query.rst
@@ -55,8 +55,8 @@ Helper methods are also provided with default values for arguments:
 The API provides both static (snapshot) and dynamic (snapshot with streaming updates) methods for a defined set of
 filter criteria:
 
-- Use ``queryBy`` to obtain a only current snapshot of data (for a given ``QueryCriteria``)
-- Use ``trackBy`` to obtain a both a current snapshot and a future stream of updates (for a given ``QueryCriteria``)
+- Use ``queryBy`` to obtain a current snapshot of data (for a given ``QueryCriteria``)
+- Use ``trackBy`` to obtain both a current snapshot and a future stream of updates (for a given ``QueryCriteria``)
   
 .. note:: Streaming updates are only filtered based on contract type and state status (UNCONSUMED, CONSUMED, ALL)
 
diff --git a/docs/source/versioning.rst b/docs/source/versioning.rst
index 9f5967e1ef..ec6d4dfae1 100644
--- a/docs/source/versioning.rst
+++ b/docs/source/versioning.rst
@@ -32,8 +32,8 @@ Flow versioning
 ---------------
 
 In addition to the evolution of the platform, flows that run on top of the platform can also evolve. It may be that the
-flow protocol between an initiating flow and it's intiated flow changes from one CorDapp release to the next in such as
-way to be backwards incompatible with existing flows. For example, if a sequence of sends and receives needs to change
+flow protocol between an initiating flow and its initiated flow changes from one CorDapp release to the next in such a
+way to be backward incompatible with existing flows. For example, if a sequence of sends and receives needs to change
 or if the semantics of a particular receive changes.
 
 The ``InitiatingFlow`` annotation (see :doc:`flow-state-machine` for more information on the flow annotations) has a ``version``