[Docs] make section title consistent

Author: ljharb

docs/rules/forbid-elements.md

@@ -53,6 +53,6 @@ React.createElement(Namespaced.Element);
 React.createElement('div', {}, React.createElement('button', {}, React.createElement('input')));
 ```
 
-## When not to use
+## When Not To Use It
 
 If you don't want to forbid any elements.

docs/rules/forbid-foreign-prop-types.md

@@ -25,7 +25,7 @@ Examples of **correct** code for this rule:
 import SomeComponent, {propTypes as someComponentPropTypes} from './SomeComponent';
 ```
 
-## When not to use
+## When Not To Use It
 
 This rule aims to make a certain production optimization, removing prop types, less prone to error. This rule may not be relevant to you if you do not wish to make use of this optimization.
 

docs/rules/forbid-prop-types.md

@@ -60,6 +60,6 @@ Whether or not to check `contextTypes` for forbidden prop types. The default val
 
 Whether or not to check `childContextTypes` for forbidden prop types. The default value is `false`.
 
-## When not to use
+## When Not To Use It
 
 This rule is a formatting/documenting preference and not following it won't negatively affect the quality of your code. This rule encourages prop types that more specifically document their usage.

docs/rules/function-component-definition.md

@@ -249,6 +249,6 @@ function getComponent() {
 
 ```
 
-## When not to use
+## When Not To Use It
 
 If you are not interested in consistent types of function components.

docs/rules/jsx-closing-bracket-location.md

@@ -212,6 +212,6 @@ var x = function() {
 </Say>;
 ```
 
-## When not to use
+## When Not To Use It
 
 If you are not using JSX then you can disable this rule.

docs/rules/jsx-closing-tag-location.md

@@ -33,6 +33,6 @@ Examples of **correct** code for this rule:
 <Hello>marklar</Hello>
 ```
 
-## When not to use
+## When Not To Use It
 
 If you do not care about closing tag JSX alignment then you can disable this rule.

docs/rules/jsx-first-prop-new-line.md

@@ -105,6 +105,6 @@ Examples of **correct** code for this rule, when configured with `"multiline-mul
 "react/jsx-first-prop-new-line": `"always" | "never" | "multiline" | "multiline-multiprop"`
 ```
 
-## When not to use
+## When Not To Use It
 
 If you are not using JSX then you can disable this rule.

docs/rules/jsx-indent-props.md

@@ -119,6 +119,6 @@ firstName="John"
 />
 ```
 
-## When not to use
+## When Not To Use It
 
 If you are not using JSX then you can disable this rule.

docs/rules/jsx-indent.md

@@ -110,6 +110,6 @@ Examples of **correct** code for this rule:
 </App>
 ```
 
-## When not to use
+## When Not To Use It
 
 If you are not using JSX then you can disable this rule.

docs/rules/jsx-key.md

@@ -57,7 +57,7 @@ Examples of **incorrect** code for this rule:
 <span {...spread} key={"key-after-spread"} />;
 ```
 
-## When not to use
+## When Not To Use It
 
 If you are not using JSX then you can disable this rule.
 

docs/rules/jsx-max-depth.md

@@ -79,6 +79,6 @@ Examples of **correct** code for this rule:
 </App>
 ```
 
-## When not to use
+## When Not To Use It
 
 If you are not using JSX then you can disable this rule.

docs/rules/jsx-max-props-per-line.md

@@ -94,6 +94,6 @@ Examples of **correct** code for this rule:
 />
 ```
 
-## When not to use
+## When Not To Use It
 
 If you are not using JSX then you can disable this rule.

docs/rules/jsx-sort-default-props.md

@@ -180,6 +180,6 @@ export default class ClassWithSpreadInPropTypes extends BaseClass {
 
 When `true` the rule ignores the case-sensitivity of the declarations order.
 
-## When not to use
+## When Not To Use It
 
 This rule is a formatting preference and not following it won't negatively affect the quality of your code. If alphabetizing `defaultProps` declarations isn't a part of your coding standards, then you can leave this rule off.

docs/rules/jsx-sort-props.md

@@ -98,6 +98,6 @@ With `reservedFirst: ["key"]`, the following will **not** warn:
 <Hello key={'uuid'} name="John" ref="ref" />
 ```
 
-## When not to use
+## When Not To Use It
 
 This rule is a formatting preference and not following it won't negatively affect the quality of your code. If alphabetizing props isn't a part of your coding standards, then you can leave this rule off.

docs/rules/no-namespace.md

@@ -24,6 +24,6 @@ The following patterns are **not** considered warnings:
 <testComponent />
 ```
 
-## When not to use
+## When Not To Use It
 
 If you are not using React.

docs/rules/sort-prop-types.md

@@ -159,6 +159,6 @@ var Component = createReactClass({
 });
 ```
 
-## When not to use
+## When Not To Use It
 
 This rule is a formatting preference and not following it won't negatively affect the quality of your code. If alphabetizing props declarations isn't a part of your coding standards, then you can leave this rule off.