diff --git a/docs/learning-from-bidict.rst b/docs/learning-from-bidict.rst
index c7ba359..5a40be5 100644
--- a/docs/learning-from-bidict.rst
+++ b/docs/learning-from-bidict.rst
@@ -137,10 +137,10 @@ Subclassing :func:`~collections.namedtuple` classes
 
 To get the performance benefits, intrinsic sortability, etc.
 of :func:`~collections.namedtuple`
-but customize behavior, state, API, etc.,
-you can subclass a :func:`~collections.namedtuple`-created class.
-Just make sure to include ``__slots__ = ()``
-or you'll lose some of the performance benefits.
+while customizing behavior, state, API, etc.,
+you can subclass a :func:`~collections.namedtuple` class.
+Just make sure to include ``__slots__ = ()``,
+or you'll lose a lot of the performance benefits.
 
 ``_marker.py`` contains a small example.
 Here's a larger one:
diff --git a/docs/other-bidict-types.rst b/docs/other-bidict-types.rst
index 7d3a849..e517661 100644
--- a/docs/other-bidict-types.rst
+++ b/docs/other-bidict-types.rst
@@ -24,12 +24,12 @@ by adding the
 :obj:`~abc.abstractproperty`. [#fn-subclasshook]_
 
 .. [#fn-subclasshook]
-    (In fact, any :class:`collections.abc.Mapping`
+    In fact, any :class:`collections.abc.Mapping`
     that provides an ``inv`` attribute
     will be considered a virtual subclass of
     :class:`bidict.BidirectionalMapping`
     :meth:`automatically <bidict.BidirectionalMapping.__subclasshook__>`,
-    enabling interoperability with external implementations.)
+    enabling interoperability with external implementations.
 
 As you may have noticed,
 :class:`bidict.bidict` is also