summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTim Hughes <timhughes@users.noreply.github.com>2018-05-20 19:14:06 +0100
committerGitHub <noreply@github.com>2018-05-20 19:14:06 +0100
commitf0b855369c5d5163e64f88e8ea3172cfa38de5c8 (patch)
tree49d25a91b75263c0904e01d9751e0c4f30716a0f
parent45faaeca7ae9da3ed4169b6d7a31df06bac4778d (diff)
downloadpytest-f0b855369c5d5163e64f88e8ea3172cfa38de5c8.tar.gz
fix typo
-rw-r--r--doc/en/logging.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/en/logging.rst b/doc/en/logging.rst
index 44cfaaa28..b2d98f547 100644
--- a/doc/en/logging.rst
+++ b/doc/en/logging.rst
@@ -123,7 +123,7 @@ You can call ``caplog.clear()`` to reset the captured log records in a test::
assert ['Foo'] == [rec.message for rec in caplog.records]
-The ``caplop.records`` attribute contains records from the current stage only, so
+The ``caplog.records`` attribute contains records from the current stage only, so
inside the ``setup`` phase it contains only setup logs, same with the ``call`` and
``teardown`` phases.