From 99072ea8c9caf1fd7ae56296b9848787d1947074 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Est=C3=A8ve?= Date: Wed, 20 Jan 2016 16:35:27 +0100 Subject: [PATCH] Fix practise -> practice typo in documentation --- README.rst | 2 +- doc/en/getting-started.rst | 2 +- doc/en/{goodpractises.rst => goodpractices.rst} | 2 +- doc/en/index.rst | 2 +- doc/en/overview.rst | 2 +- doc/en/writing_plugins.rst | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) rename doc/en/{goodpractises.rst => goodpractices.rst} (99%) diff --git a/README.rst b/README.rst index 34fad1660..6465bd756 100644 --- a/README.rst +++ b/README.rst @@ -60,7 +60,7 @@ Features - Detailed info on failing `assert statements `_ (no need to remember ``self.assert*`` names); - `Auto-discovery - `_ + `_ of test modules and functions; - `Modular fixtures `_ for diff --git a/doc/en/getting-started.rst b/doc/en/getting-started.rst index f91c38de9..a4814d196 100644 --- a/doc/en/getting-started.rst +++ b/doc/en/getting-started.rst @@ -193,7 +193,7 @@ Where to go next Here are a few suggestions where to go next: * :ref:`cmdline` for command line invocation examples -* :ref:`good practises ` for virtualenv, test layout, genscript support +* :ref:`good practices ` for virtualenv, test layout, genscript support * :ref:`fixtures` for providing a functional baseline to your tests * :ref:`apiref` for documentation and examples on using ``pytest`` * :ref:`plugins` managing and writing plugins diff --git a/doc/en/goodpractises.rst b/doc/en/goodpractices.rst similarity index 99% rename from doc/en/goodpractises.rst rename to doc/en/goodpractices.rst index b2c34bae9..2d8050bd9 100644 --- a/doc/en/goodpractises.rst +++ b/doc/en/goodpractices.rst @@ -1,5 +1,5 @@ .. highlightlang:: python -.. _`goodpractises`: +.. _`goodpractices`: Good Integration Practices ================================================= diff --git a/doc/en/index.rst b/doc/en/index.rst index 7fb80aaa2..09e342e22 100644 --- a/doc/en/index.rst +++ b/doc/en/index.rst @@ -40,7 +40,7 @@ pytest: helps you write better programs - multi-paradigm: pytest can run ``nose``, ``unittest`` and ``doctest`` style test suites, including running testcases made for Django and trial - - supports :ref:`good integration practises ` + - supports :ref:`good integration practices ` - supports extended :ref:`xUnit style setup ` - supports domain-specific :ref:`non-python tests` - supports generating `test coverage reports diff --git a/doc/en/overview.rst b/doc/en/overview.rst index 9d8390f52..eb2619775 100644 --- a/doc/en/overview.rst +++ b/doc/en/overview.rst @@ -7,7 +7,7 @@ Getting started basics getting-started usage - goodpractises + goodpractices projects faq diff --git a/doc/en/writing_plugins.rst b/doc/en/writing_plugins.rst index 0321b9402..110ffd93b 100644 --- a/doc/en/writing_plugins.rst +++ b/doc/en/writing_plugins.rst @@ -95,7 +95,7 @@ Here is how you might run it:: python package directory (i.e. one containing an ``__init__.py``) then "import conftest" can be ambiguous because there might be other ``conftest.py`` files as well on your PYTHONPATH or ``sys.path``. - It is thus good practise for projects to either put ``conftest.py`` + It is thus good practice for projects to either put ``conftest.py`` under a package scope or to never import anything from a conftest.py file.