Skip to content

Commit 0527a96

Browse files
authored
Merge pull request #239 from felixonmars/patch-1
Fix some typos in README
2 parents 5684b36 + 11df9bf commit 0527a96

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -392,7 +392,7 @@ But in much cleaner and powerful way:
392392
Then the text should be parsed with correct indentation
393393
394394
Step is considered as multiline one, if the **next** line(s) after it's first line, is indented relatively
395-
to the first line. The step name is then simply extended by adding futher lines with newlines.
395+
to the first line. The step name is then simply extended by adding further lines with newlines.
396396
In the example above, the Given step name will be:
397397

398398
.. code-block:: python
@@ -723,7 +723,7 @@ completely different:
723723

724724
For picking up tests to run we can use
725725
`tests selection <http://pytest.org/latest/usage.html#specifying-tests-selecting-tests>`_ technique. The problem is that
726-
you have to know how your tests are organized, knowing ony the feature files organization is not enough.
726+
you have to know how your tests are organized, knowing only the feature files organization is not enough.
727727
`cucumber tags <https://github.com/cucumber/cucumber/wiki/Tags>`_ introduce standard way of categorizing your features
728728
and scenarios, which pytest-bdd supports. For example, we could have:
729729

@@ -1080,7 +1080,7 @@ test_publish_article.py:
10801080
return False
10811081
10821082
1083-
@scenario('publish_article.feature', 'Publishing the article in a wierd way')
1083+
@scenario('publish_article.feature', 'Publishing the article in a weird way')
10841084
def test_publish():
10851085
pass
10861086

0 commit comments

Comments
 (0)