Skip to content

Commit 0c6f34e

Browse files
committed
hack
1 parent 08e4358 commit 0c6f34e

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ started with testdouble.js:
6161
Its outline is in [docs/README.md](/docs#readme)
6262

6363
Of course, if you're unsure of how to approach writing an isolated test with
64-
testdouble.js, we welcome you to [open a issue on GitHub to ask a
64+
testdouble.js, we welcome you to [open an issue on GitHub to ask a
6565
question](https://github.com/testdouble/testdouble.js/issues/new).
6666

6767
## API
@@ -71,13 +71,13 @@ question](https://github.com/testdouble/testdouble.js/issues/new).
7171
The first thing a test double library needs to do is give you a way to replace
7272
the production dependencies of your [subject under
7373
test](https://github.com/testdouble/contributing-tests/wiki/Subject) with fake
74-
ones created by the library.
74+
ones controlled by your test.
7575

7676
We provide a top-level method called `td.replace()` that operates in two
7777
different modes: CommonJS module replacement and object-property replacement.
78-
Both modes will, by default, perform a deep clone the real dependency but
79-
replace all of its functions with fake test double functions that you can
80-
configure and observe.
78+
Both modes will, by default, perform a deep clone the real dependency which
79+
replaces all functions it encounters with fake test double functions that can be
80+
configured by your test to either stub responses or assert invocations.
8181

8282
#### Module replacement with Node.js
8383

0 commit comments

Comments
 (0)