Skip to content
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

Documentation typo fix #4389

Merged
merged 2 commits into from
Jan 10, 2018
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
2 changes: 1 addition & 1 deletion element/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ You may find yourself asking, "Why an abstraction layer?". For a few reasons:
- It provides a mechanism to shield implementers by omitting features with uncertain futures (`createClass`, `PropTypes`).
- It helps avoid incompatibilities between versions by ensuring that every plugin operates on a single centralized version of the code.

On the `wp.element` global object, you will find the following, ordered roughly be likelihood you'll encounter it in your code:
On the `wp.element` global object, you will find the following, ordered roughly by the likelihood you'll encounter it in your code:

- [`createElement`](https://facebook.github.io/react/docs/react-api.html#createelement)
- [`render`](https://facebook.github.io/react/docs/react-dom.html#render)
Expand Down