python-postgres
diff --git a/‎postgresql/documentation/driver.txt‎
Lines changed: 2 additions & 2 deletions b/‎postgresql/documentation/driver.txt‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎postgresql/documentation/gotchas.txt‎
Lines changed: 3 additions & 3 deletions b/‎postgresql/documentation/gotchas.txt‎
Lines changed: 3 additions & 3 deletions
@@ -1645,8 +1645,8 @@ object relationship model provides a common protocol for controlling message
 propagation and, ultimately, display.
 
 The ``msghook`` attribute on elements is absent by default. However, when
-present on an object--explicitly set--that contributed the cause of a message
-event, it will be invoked with the Message, `postgresql.api.Message`, object as
+present on an object that contributed the cause of a message event, it will
+be invoked with the Message, `postgresql.api.Message`, object as
 its sole parameter. The attribute of the object that is closest to the event is
 checked first, if present it will be called. If the ``msghook()`` call returns
 a `True` value(specficially, ``bool(x) is True``), the message will not be
 
@@ -6,8 +6,8 @@ given user. In order to highlight those potential issues and hopefully bring
 some sense into a confusing situation, this document was drawn.
 
 
-client_encoding setting should be altered carefully
----------------------------------------------------
+`client_encoding` setting should be altered carefully
+-----------------------------------------------------
 
 `postgresql.driver`'s streaming cursor implementation reads a fixed set of rows
 when it queries the server for more. In order to optimize some situations, the
@@ -22,7 +22,7 @@ Furthermore, it is probably best to never change the `client_encoding` as the
 driver automatically makes the necessary transformation to Python strings.
 
 
-The user and password is correct, but does it not work when using `postgresql.driver`
+The user and password is correct, but it does not work when using `postgresql.driver`
 -------------------------------------------------------------------------------------
 
 This issue likely comes from the possibility that the information sent to the