docs: fixup small wording issues

Author: RebeccaStevens

CONTRIBUTING.md

@@ -16,7 +16,7 @@ In order to know which AST nodes are created for a snippet of TypeScript code yo
 
 > tl;dr: use `npx cz` instead of `git commit`.
 
-Commit messages must follow [Conventional Commit messages guidelines](https://www.conventionalcommits.org/en/v1.0.0/). You can use `npx cz` instead of `git commit` to run a interactive prompt to generate the commit message. We've customize the prompt specifically for this project. For more information see [commitizen](https://github.com/commitizen/cz-cli#readme).
+Commit messages must follow [Conventional Commit messages guidelines](https://www.conventionalcommits.org/en/v1.0.0/). You can use `npx cz` instead of `git commit` to run an interactive prompt to generate the commit message. We've customize the prompt specifically for this project. For more information see [commitizen](https://github.com/commitizen/cz-cli#readme).
 
 ### How to publish
 

GETTING_STARTED.md

@@ -42,7 +42,7 @@ Add `functional` to the plugins section of your `.eslintrc` configuration file.
 ```
 
 There are several rulesets provided by this plugin.
-[See below](#rulesets) for what they are and what rules are including in each.
+[See below](#rulesets) for what they are and what rules are included in each.
 Enable rulesets via the "extends" property of your `.eslintrc` configuration file.
 
 ```jsonc

README.md

@@ -116,11 +116,11 @@ The [below section](#rules) gives details on which rules are enabled by each rul
 
 ### No Other Paradigms
 
-| Name                                                     | Description                                                                  | 💼                                     | ⚠️  | 🚫    | 🔧  | 💡  | ❌  |
-| :------------------------------------------------------- | :--------------------------------------------------------------------------- | :------------------------------------- | :-- | :---- | :-- | :-- | :-- |
-| [no-classes](docs/rules/no-classes.md)                   | Disallow classes.                                                            | ☑️ ![badge-no-other-paradigms][] ✅ 🔒 |     |       |     |     |     |
-| [no-mixed-types](docs/rules/no-mixed-types.md)           | Restrict types so that only members of the same kind of are allowed in them. | ☑️ ![badge-no-other-paradigms][] ✅ 🔒 |     |       |     |     |     |
-| [no-this-expressions](docs/rules/no-this-expressions.md) | Disallow this access.                                                        | ![badge-no-other-paradigms][] 🔒       |     | ☑️ ✅ |     |     |     |
+| Name                                                     | Description                                                               | 💼                                     | ⚠️  | 🚫    | 🔧  | 💡  | ❌  |
+| :------------------------------------------------------- | :------------------------------------------------------------------------ | :------------------------------------- | :-- | :---- | :-- | :-- | :-- |
+| [no-classes](docs/rules/no-classes.md)                   | Disallow classes.                                                         | ☑️ ![badge-no-other-paradigms][] ✅ 🔒 |     |       |     |     |     |
+| [no-mixed-types](docs/rules/no-mixed-types.md)           | Restrict types so that only members of the same kind are allowed in them. | ☑️ ![badge-no-other-paradigms][] ✅ 🔒 |     |       |     |     |     |
+| [no-this-expressions](docs/rules/no-this-expressions.md) | Disallow this access.                                                     | ![badge-no-other-paradigms][] 🔒       |     | ☑️ ✅ |     |     |     |
 
 ### No Statements
 

docs/rules/functional-parameters.md

@@ -4,7 +4,7 @@
 
 <!-- end auto-generated rule header -->
 
-Disallow use of rest parameters, the `arguments` keyword and enforces that functions take a least 1 parameter.
+Disallow use of rest parameters, the `arguments` keyword and enforces that functions take at least 1 parameter.
 
 ## Rule Details
 
@@ -130,7 +130,7 @@ There's not much point of having a function that doesn't take any parameters in
 
 Require all functions to have exactly one parameter.
 
-Any function that take takes multiple parameter can be rewritten as a higher-order function that only takes one.
+Any function that takes multiple parameter can be rewritten as a higher-order function that only takes one.
 
 Example:
 

docs/rules/immutable-data.md

@@ -94,7 +94,7 @@ const liteOptions = {
 
 ### `assumeTypes`
 
-The rule take advantage of TypeScript's typing engine to check if mutation is taking place.
+The rule takes advantage of TypeScript's typing engine to check if mutation is taking place.
 If you are not using TypeScript, type checking cannot be performed; hence this option exists.
 
 This option will make the rule assume the type of the nodes it is checking are of type Array/Object.

docs/rules/no-classes.md

@@ -66,7 +66,7 @@ Instead of creating classes, you should use React 0.14's [Stateless Functional C
 const Message = ({ message }) => <div>{message}</div>;
 ```
 
-What about lifecycle methods like `shouldComponentUpdate`? We can use the [recompose](https://github.com/acdlite/recompose) library to apply these optimizations to your Stateless Functional Components. The [recompose](https://github.com/acdlite/recompose) library relies on the fact that your Redux state is immutable to efficiently implement shouldComponentUpdate for you.
+What about lifecycle methods like `shouldComponentUpdate`? We can use the [recompose](https://github.com/acdlite/recompose) library to apply these optimizations to your Stateless Functional Components. The [recompose](https://github.com/acdlite/recompose) library relies on the fact that your Redux state is immutable to efficiently implement `shouldComponentUpdate` for you.
 
 ```js
 import { pure, onlyUpdateForKeys } from "recompose";

docs/rules/no-mixed-types.md

@@ -1,4 +1,4 @@
-# Restrict types so that only members of the same kind of are allowed in them (`functional/no-mixed-types`)
+# Restrict types so that only members of the same kind are allowed in them (`functional/no-mixed-types`)
 
 💼 This rule is enabled in the following configs: ☑️ `lite`, `no-other-paradigms`, ✅ `recommended`, 🔒 `strict`.
 

docs/rules/no-this-expressions.md

@@ -6,7 +6,7 @@
 
 ## Rule Details
 
-This rule is companion rule to the [no-classes](./no-classes.md) rule.
+This rule is a companion rule to the [no-classes](./no-classes.md) rule.
 See the its docs for more info.
 
 ### ❌ Incorrect

docs/rules/prefer-immutable-types.md

@@ -10,7 +10,7 @@
 
 This rule is deigned to be a replacement for
 [@typescript-eslint/prefer-readonly-parameter-types](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/prefer-readonly-parameter-types.md)
-but also add extra functionality, allowing not just parameters to checked.
+but also add extra functionality, allowing not just parameters to be checked.
 
 This rule uses the
 [is-immutable-type](https://www.npmjs.com/package/is-immutable-type) library to

docs/rules/prefer-property-signatures.md

@@ -11,7 +11,7 @@ There are two ways function members can be declared in interfaces and type alias
 The `MethodSignature` and the `PropertySignature` forms seem equivalent, but only the `PropertySignature` form can have a `readonly` modifier.
 Because of this any `MethodSignature` will be mutable unless wrapped in the `Readonly` type.
 
-It should be noted however that the `PropertySignature` do not support overloading.
+It should be noted however that the `PropertySignature` form does not support overloading.
 
 ### ❌ Incorrect