Skip to content

Commit

Permalink
[docs] Grammar fixes.
Browse files Browse the repository at this point in the history
Closes #565, #566, #568, #569, #570.
  • Loading branch information
ljharb committed Apr 27, 2016
1 parent c624783 commit da6b3ce
Show file tree
Hide file tree
Showing 5 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion docs/rules/jsx-max-props-per-line.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ Limiting the maximum of props on a single line can improve readability.

## Rule Details

This rule checks all JSX elements and verifies that the number of props per line do not exceed the maximum allowed. A spread attribute count as one prop. This rule is off by default and when on the default maximum of props on one line is `1`.
This rule checks all JSX elements and verifies that the number of props per line do not exceed the maximum allowed. A spread attribute counts as one prop. This rule is off by default and when on the default maximum of props on one line is `1`.

The following patterns are considered warnings:

Expand Down
2 changes: 1 addition & 1 deletion docs/rules/jsx-no-undef.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Disallow undeclared variables in JSX (jsx-no-undef)

This rules can help you locate potential ReferenceErrors resulting from misspellings or missing components.
This rule helps locate potential ReferenceErrors resulting from misspellings or missing components.

## Rule Details

Expand Down
4 changes: 2 additions & 2 deletions docs/rules/jsx-uses-vars.md
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# Prevent variables used in JSX to be incorrectly marked as unused (jsx-uses-vars)

Since 0.17.0 the ESLint `no-unused-vars` rule does not detect variables used in JSX ([see details](http://eslint.org/blog/2015/03/eslint-0.17.0-released/#changes-to-jsx/react-handling)). This rules will find variables used in JSX and mark them as used.
Since 0.17.0 the ESLint `no-unused-vars` rule does not detect variables used in JSX ([see details](http://eslint.org/blog/2015/03/eslint-0.17.0-released/#changes-to-jsx/react-handling)). This rule will find variables used in JSX and mark them as used.

This rule has no effect if the `no-unused-vars` rule is not enabled.
This rule only has an effect when the `no-unused-vars` rule is enabled.

## Rule Details

Expand Down
2 changes: 1 addition & 1 deletion docs/rules/no-string-refs.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Prevent using string references (no-string-refs)

Currently, two ways are supported by React to refer to components. The first one, providing a string identifier is considered legacy in the official documentation. Referring to components by setting an property on the `this` object in the reference callback is preferred.
Currently, two ways are supported by React to refer to components. The first one, providing a string identifier is considered legacy in the official documentation. Referring to components by setting a property on the `this` object in the reference callback is preferred.

## Rule Details

Expand Down
2 changes: 1 addition & 1 deletion docs/rules/require-render-return.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Enforce ES5 or ES6 class for returning value in render function (require-render-return)

When writing the `render` method in a component it could be easy to forgot to return the JSX content. This rule will warn you if the `return` statement is missing.
When writing the `render` method in a component it is easy to forget to return the JSX content. This rule will warn if the `return` statement is missing.

## Rule Details

Expand Down

0 comments on commit da6b3ce

Please sign in to comment.