Skip to content

Fix some typos #149

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 18, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/react-testing-library/api.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,17 +52,17 @@ test('renders a message', () => {

## `render` Options

You wont often need to specify options, but if you ever do, here are the
You won't often need to specify options, but if you ever do, here are the
available options which you could provide as a second argument to `render`.

### `container`

By default, `React Testing Library` will create a `div` and append that div to
the `document.body` and this is where your react component will be rendered. If
By default, `React Testing Library` will create a `div` and append that `div` to
the `document.body` and this is where your React component will be rendered. If
you provide your own HTMLElement `container` via this option, it will not be
appended to the `document.body` automatically.

For Example: If you are unit testing a `tablebody` element, it cannot be a child
For example: If you are unit testing a `tablebody` element, it cannot be a child
of a `div`. In this case, you can specify a `table` as the render `container`.

```jsx
Expand Down