Apply suggestions from code review

Co-authored-by: Dmitri Popov <[email protected]>

Author: dcermak

source/usage.rst

@@ -463,21 +463,20 @@ upstream documentation:
 <https://docs.pytest.org/en/latest/example/markers.html#mark-examples>_
 
 It can be beneficial to mark each container for a test suite with a unique
-marker, so that you can run the tests only for a single container image. This
-would involve wrapping each :py:class:`~pytest_container.container.Container`
+marker, so that you can run the tests only for a single container image. This involves wrapping each :py:class:`~pytest_container.container.Container`
 and :py:class:`~pytest_container.container.DerivedContainer` in a
 ``pytest.param()``. This approach two disadvantages:
 
 1. you are now handling ``pytest.ParameterSet`` instance and have to unpack them
    to access the underlying :py:class:`~pytest_container.container.Container`
    and :py:class:`~pytest_container.container.DerivedContainer`
 
-2. :py:class:`~pytest_container.container.DerivedContainer` do not "inherit" the
+2. :py:class:`~pytest_container.container.DerivedContainer` does not "inherit" the
    marks from their base containers. This has proven to be a very annoying
    limitation in practice.
 
 To remedy this, :py:class:`~pytest_container.container.ContainerBase` now
-inherits from ``pytest.ParameterSet`` and can itself take marks via the
+inherits from ``pytest.ParameterSet`` and can itself accept marks via the
 constructor. These marks automatically carry over into
 :py:class:`~pytest_container.container.DerivedContainer` instances: