From ca802d006a5b44863740a8c894e1f456aa66afd5 Mon Sep 17 00:00:00 2001 From: Michael Foord Date: Fri, 13 Apr 2012 20:43:06 +0100 Subject: Doc fixes --- docs/getting-started.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/getting-started.txt b/docs/getting-started.txt index b873e20..1b5d289 100644 --- a/docs/getting-started.txt +++ b/docs/getting-started.txt @@ -50,7 +50,7 @@ and attributes that allow you to make assertions about how it has been used. Once the mock has been called its :attr:`~Mock.called` attribute is set to `True`. More importantly we can use the :meth:`~Mock.assert_called_with` or -:meth`~Mock.assert_called_once_with` method to check that it was called with +:meth:`~Mock.assert_called_once_with` method to check that it was called with the correct arguments. This example tests that calling `ProductionClass().method` results in a call to @@ -117,7 +117,7 @@ by looking at the return value of the mocked class. In the example below we have a function `some_function` that instantiates `Foo` and calls a method on it. The call to `patch` replaces the class `Foo` with a mock. The `Foo` instance is the result of calling the mock, so it is configured -by modify the mock :attr:`~Mock.return_value`. +by modifying the mock :attr:`~Mock.return_value`. .. doctest:: -- cgit v1.2.1