@@ -42,7 +42,7 @@ your hook. We currently support two different renderers:
42
42
- ` react-test-renderer `
43
43
- ` react-dom `
44
44
45
- When using standard import for this library (show below), we will attempt to auto-detect which
45
+ When using standard import for this library (see below), we will attempt to auto-detect which
46
46
renderer you have installed and use it without needing any specific wiring up to make it happen. If
47
47
you have both installed in your project, and you use the standard import (see below) the library
48
48
will default to using ` react-test-renderer ` .
@@ -63,7 +63,7 @@ import { renderHook } from '@testing-library/react-hooks'
63
63
### Act
64
64
65
65
Each render also provides a unique [ ` act ` function] ( https://reactjs.org/docs/test-utils.html#act )
66
- that cannot be used with other renderers. In order to simplify with ` act ` function you need to use,
66
+ that cannot be used with other renderers. In order to simplify which ` act ` function you need to use,
67
67
we also export the correct one alongside the detected renderer for you:
68
68
69
69
``` js
@@ -73,8 +73,8 @@ import { renderHook, act } from '@testing-library/react-hooks'
73
73
## Being specific
74
74
75
75
Auto-detection is great for simplifying setup and getting out of your way, but sometimes you do need
76
- a little but more control. If a test needs requires a specific type of environment, the import can
77
- be appended to force a specific renderer to be use . The supported environments are:
76
+ a little bit more control. If a test needs a specific type of environment, the import can
77
+ be appended to force a specific renderer to be used . The supported environments are:
78
78
79
79
- ` dom `
80
80
- ` native `
0 commit comments