[Docs] Fix typos

Author: bmish

CHANGELOG.md

@@ -2673,7 +2673,7 @@ React ([#1073][] @jomasti)
 ### Fixed
 * Fix [`jsx-closing-bracket-location`][] fixer ([#533][] @dtinth)
 * Fix [`require-render-return`][] to only check valid render methods ([#563][])
-* Fix detection to allow simple `this` usage in fonctional components ([#576][])
+* Fix detection to allow simple `this` usage in functional components ([#576][])
 * Fix [`forbid-prop-types`][] crash ([#579][])
 * Fix comment handling in [`jsx-curly-spacing`][] ([#584][])
 
@@ -3693,7 +3693,7 @@ If you're still not using React 15 you can keep the old behavior by setting the
 * Add [`jsx-uses-react`][] rule ([#6][] @glenjamin)
 
 ### Changed
-* Update [`prop-types`][] to check props usage insead of propTypes presence ([#4][])
+* Update [`prop-types`][] to check props usage instead of propTypes presence ([#4][])
 
 [1.4.0]: https://github.com/jsx-eslint/eslint-plugin-react/compare/v1.3.0...v1.4.0
 [#4]: https://github.com/jsx-eslint/eslint-plugin-react/issues/4

docs/rules/jsx-props-no-spreading.md

@@ -68,7 +68,7 @@ Examples of **incorrect** code for this rule, when `custom` is set to `ignore`:
 
 ### explicitSpread
 
-`explicitSpread` set to `ignore` will ignore spread operators that are explicilty listing all object properties within that spread. Default is set to `enforce`.
+`explicitSpread` set to `ignore` will ignore spread operators that are explicitly listing all object properties within that spread. Default is set to `enforce`.
 
 Examples of **correct** code for this rule, when `explicitSpread` is set to `ignore`:
 

docs/rules/no-arrow-function-lifecycle.md

@@ -2,7 +2,7 @@
 
 🔧 This rule is automatically fixable using the `--fix` [flag](https://eslint.org/docs/latest/user-guide/command-line-interface#--fix) on the command line.
 
-It is not neccessary to use arrow function for lifecycle methods. This makes things harder to test, conceptually less performant (although in practice, performance will not be affected, since most engines will optimize efficiently), and can break hot reloading patterns.
+It is not necessary to use arrow function for lifecycle methods. This makes things harder to test, conceptually less performant (although in practice, performance will not be affected, since most engines will optimize efficiently), and can break hot reloading patterns.
 
 ## Rule Details
 

docs/rules/no-unstable-nested-components.md

@@ -2,7 +2,7 @@
 
 Creating components inside components without memoization leads to unstable components. The nested component and all its children are recreated during each re-render. Given stateful children of the nested component will lose their state on each re-render.
 
-React reconcilation performs element type comparison with [reference equality](https://github.com/facebook/react/blob/v16.13.1/packages/react-reconciler/src/ReactChildFiber.js#L407). The reference to the same element changes on each re-render when defining components inside the render block. This leads to complete recreation of the current node and all its children. As a result the virtual DOM has to do extra unnecessary work and [possible bugs are introduced](https://codepen.io/ariperkkio/pen/vYLodLB).
+React reconciliation performs element type comparison with [reference equality](https://github.com/facebook/react/blob/v16.13.1/packages/react-reconciler/src/ReactChildFiber.js#L407). The reference to the same element changes on each re-render when defining components inside the render block. This leads to complete recreation of the current node and all its children. As a result the virtual DOM has to do extra unnecessary work and [possible bugs are introduced](https://codepen.io/ariperkkio/pen/vYLodLB).
 
 ## Rule Details
 

docs/rules/sort-prop-types.md

@@ -1,6 +1,6 @@
 # Enforce propTypes declarations alphabetical sorting (react/sort-prop-types)
 
-Some developers prefer to sort prop type declaratioms alphabetically to be able to find necessary declaration easier at the later time. Others feel that it adds complexity and becomes burden to maintain.
+Some developers prefer to sort prop type declarations alphabetically to be able to find necessary declaration easier at the later time. Others feel that it adds complexity and becomes burden to maintain.
 
 ## Rule Details
 

lib/rules/jsx-curly-brace-presence.js

@@ -138,8 +138,8 @@ module.exports = {
       )).join(HTML_ENTITY);
 
       const htmlEntities = text.match(HTML_ENTITY_REGEX());
-      return htmlEntities.reduce((acc, htmlEntitiy) => (
-        acc.replace(HTML_ENTITY, htmlEntitiy)
+      return htmlEntities.reduce((acc, htmlEntity) => (
+        acc.replace(HTML_ENTITY, htmlEntity)
       ), withCurlyBraces);
     }
 
@@ -244,8 +244,8 @@ module.exports = {
     }
 
     // Bail out if there is any character that needs to be escaped in JSX
-    // because escaping decreases readiblity and the original code may be more
-    // readible anyway or intentional for other specific reasons
+    // because escaping decreases readability and the original code may be more
+    // readable anyway or intentional for other specific reasons
     function lintUnnecessaryCurly(JSXExpressionNode) {
       const expression = JSXExpressionNode.expression;
       const expressionType = expression.type;

lib/rules/no-access-state-in-setstate.js

@@ -130,7 +130,7 @@ module.exports = {
               break;
             }
 
-            // Storing all variables containg this.state
+            // Storing all variables containing this.state
             if (current.type === 'VariableDeclarator') {
               vars.push({
                 node,

lib/rules/no-danger.js

@@ -29,7 +29,7 @@ const DANGEROUS_PROPERTIES = fromEntries(DANGEROUS_PROPERTY_NAMES.map((prop) =>
 /**
  * Checks if a JSX attribute is dangerous.
  * @param {String} name - Name of the attribute to check.
- * @returns {boolean} Whether or not the attribute is dnagerous.
+ * @returns {boolean} Whether or not the attribute is dangerous.
  */
 function isDangerous(name) {
   return has(DANGEROUS_PROPERTIES, name);

lib/rules/no-direct-mutation-state.js

@@ -56,7 +56,7 @@ module.exports = {
     }
 
     /**
-     * Walks throughs the MemberExpression to the top-most property.
+     * Walks through the MemberExpression to the top-most property.
      * @param {Object} node The node to process
      * @returns {Object} The outer-most MemberExpression
      */

lib/rules/no-unescaped-entities.js

@@ -81,7 +81,7 @@ module.exports = {
       const configuration = context.options[0] || {};
       const entities = configuration.forbid || DEFAULTS;
 
-      // HTML entites are already escaped in node.value (as well as node.raw),
+      // HTML entities are already escaped in node.value (as well as node.raw),
       // so pull the raw text from context.getSourceCode()
       for (let i = node.loc.start.line; i <= node.loc.end.line; i++) {
         let rawLine = context.getSourceCode().lines[i - 1];