[Docs] HTTP => HTTPS

Author: Schweinepriester

CHANGELOG.md

@@ -1,7 +1,7 @@
 # Change Log
 All notable changes to this project will be documented in this file.
-This project adheres to [Semantic Versioning](http://semver.org/).
-This change log adheres to standards from [Keep a CHANGELOG](http://keepachangelog.com).
+This project adheres to [Semantic Versioning](https://semver.org/).
+This change log adheres to standards from [Keep a CHANGELOG](https://keepachangelog.com).
 
 ## Unreleased
 
@@ -13,9 +13,11 @@ This change log adheres to standards from [Keep a CHANGELOG](http://keepachangel
 
 ### Changed
 * [readme] change [`jsx-runtime`] link from branch to sha ([#3160][] @tatsushitoji)
+* [Docs] HTTP => HTTPS ([#3133][] @Schweinepriester)
 
 [#3163]: https://github.com/yannickcr/eslint-plugin-react/pull/3163
 [#3160]: https://github.com/yannickcr/eslint-plugin-react/pull/3160
+[#3133]: https://github.com/yannickcr/eslint-plugin-react/pull/3133
 [#2921]: https://github.com/yannickcr/eslint-plugin-react/pull/2921
 
 ## [7.28.0] - 2021.12.22
@@ -2189,7 +2191,7 @@ React ([#1073][] @jomasti)
 * Add support for `PureComponent` in [`prefer-stateless-function`][] ([#781][] @tiemevanveen)
 
 ### Fixed
-* Fix [`jsx-uses-vars`][] to work better with [`prefer-const`](http://eslint.org/docs/rules/prefer-const). You'll need to upgrade to ESLint 3.4.0 to completely fix the compatibility issue ([#716][])
+* Fix [`jsx-uses-vars`][] to work better with [`prefer-const`](https://eslint.org/docs/rules/prefer-const). You'll need to upgrade to ESLint 3.4.0 to completely fix the compatibility issue ([#716][])
 * Fix [`require-render-return`][] crash ([#784][])
 * Fix related components detection in [`prop-types`][] ([#735][])
 * Fix component detection to ignore functions expression without a parent component

README.md

@@ -262,11 +262,11 @@ This pairs well with the `eslint:all` rule.
 }
 ```
 
-**Note**: These configurations will import `eslint-plugin-react` and enable JSX in [parser options](http://eslint.org/docs/user-guide/configuring#specifying-parser-options).
+**Note**: These configurations will import `eslint-plugin-react` and enable JSX in [parser options](https://eslint.org/docs/user-guide/configuring/language-options#specifying-parser-options).
 
 # License
 
-`eslint-plugin-react` is licensed under the [MIT License](http://www.opensource.org/licenses/mit-license.php).
+`eslint-plugin-react` is licensed under the [MIT License](https://opensource.org/licenses/mit-license.php).
 
 
 [npm-url]: https://npmjs.org/package/eslint-plugin-react

docs/rules/boolean-prop-naming.md

@@ -118,5 +118,5 @@ This value is boolean. It tells if nested props should be validated as well. By
 ```
 
 [PropTypes]: https://reactjs.org/docs/typechecking-with-proptypes.html
-[TypeScript]: http://www.typescriptlang.org/
+[TypeScript]: https://www.typescriptlang.org/
 [Flow]: https://flow.org/

docs/rules/default-props-match-prop-types.md

@@ -196,5 +196,5 @@ If you don't care about stray `defaultsProps` in your components, you can disabl
 - [Official React documentation on defaultProps](https://facebook.github.io/react/docs/typechecking-with-proptypes.html#default-prop-values)
 
 [PropTypes]: https://reactjs.org/docs/typechecking-with-proptypes.html
-[TypeScript]: http://www.typescriptlang.org/
+[TypeScript]: https://www.typescriptlang.org/
 [Flow]: https://flow.org/

docs/rules/jsx-curly-spacing.md

@@ -219,7 +219,7 @@ Examples of **correct** code for this rule, when configured with `"never"` and `
 <App blah={3} foo={ {bar: true, baz: true} } />;
 ```
 
-Please note that spacing of the object literal curly braces themselves is controlled by the built-in [`object-curly-spacing`](http://eslint.org/docs/rules/object-curly-spacing) rule.
+Please note that spacing of the object literal curly braces themselves is controlled by the built-in [`object-curly-spacing`](https://eslint.org/docs/rules/object-curly-spacing) rule.
 
 ### Shorthand options
 

docs/rules/jsx-no-target-blank.md

@@ -37,16 +37,16 @@ This rule aims to prevent user generated link hrefs and form actions from creati
 Examples of **incorrect** code for this rule, when configured with `{ "enforceDynamicLinks": "always" }`:
 
 ```jsx
-var Hello = <a target='_blank' href="http://example.com/"></a>
+var Hello = <a target='_blank' href="https://example.com/"></a>
 var Hello = <a target='_blank' href={dynamicLink}></a>
 ```
 
 Examples of **correct** code for this rule:
 
 ```jsx
 var Hello = <p target="_blank"></p>
-var Hello = <a target="_blank" rel="noreferrer" href="http://example.com"></a>
-var Hello = <a target="_blank" rel="noopener noreferrer" href="http://example.com"></a>
+var Hello = <a target="_blank" rel="noreferrer" href="https://example.com"></a>
+var Hello = <a target="_blank" rel="noopener noreferrer" href="https://example.com"></a>
 var Hello = <a target="_blank" href="relative/path/in/the/host"></a>
 var Hello = <a target="_blank" href="/absolute/path/in/the/host"></a>
 var Hello = <a></a>
@@ -68,7 +68,7 @@ Spread attributes are a handy way of passing programmatically-generated props to
 
 ```jsx
 const unsafeProps = {
-  href: "http://example.com",
+  href: "https://example.com",
   target: "_blank",
 };
 
@@ -88,13 +88,13 @@ Defaults to false. If false, this rule will ignore all spread attributes. If tru
 When option `forms` is set to `true`, the following is considered an error:
 
 ```jsx
-var Hello = <form target="_blank" action="http://example.com/"></form>;
+var Hello = <form target="_blank" action="https://example.com/"></form>;
 ```
 
 When option `links` is set to `true`, the following is considered an error:
 
 ```jsx
-var Hello = <a target='_blank' href="http://example.com/"></form>
+var Hello = <a target='_blank' href="https://example.com/"></form>
 ```
 
 ### Custom link components
@@ -104,14 +104,14 @@ This rule supports the ability to use custom components for links, such as `<Lin
 Examples of **incorrect** code for this rule:
 
 ```jsx
-var Hello = <Link target="_blank" to="http://example.com/"></Link>
+var Hello = <Link target="_blank" to="https://example.com/"></Link>
 var Hello = <Link target="_blank" to={dynamicLink}></Link>
 ```
 
 Examples of **correct** code for this rule:
 
 ```jsx
-var Hello = <Link target="_blank" rel="noopener noreferrer" to="http://example.com"></Link>
+var Hello = <Link target="_blank" rel="noopener noreferrer" to="https://example.com"></Link>
 var Hello = <Link target="_blank" to="relative/path/in/the/host"></Link>
 var Hello = <Link target="_blank" to="/absolute/path/in/the/host"></Link>
 var Hello = <Link />

docs/rules/jsx-uses-vars.md

@@ -1,6 +1,6 @@
 # Prevent variables used in JSX to be incorrectly marked as unused (react/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-jsxreact-handling)). This rule 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](https://eslint.org/blog/2015/03/eslint-0.17.0-released#changes-to-jsxreact-handling)). This rule will find variables used in JSX and mark them as used.
 
 This rule only has an effect when the `no-unused-vars` rule is enabled.
 

docs/rules/no-render-return-value.md

@@ -1,6 +1,6 @@
 # Prevent usage of the return value of ReactDOM.render (react/no-render-return-value)
 
-> `ReactDOM.render()` currently returns a reference to the root `ReactComponent` instance. However, using this return value is legacy and should be avoided because future versions of React may render components asynchronously in some cases. If you need a reference to the root `ReactComponent` instance, the preferred solution is to attach a [callback ref](http://facebook.github.io/react/docs/more-about-refs.html#the-ref-callback-attribute) to the root element.
+> `ReactDOM.render()` currently returns a reference to the root `ReactComponent` instance. However, using this return value is legacy and should be avoided because future versions of React may render components asynchronously in some cases. If you need a reference to the root `ReactComponent` instance, the preferred solution is to attach a [callback ref](https://reactjs.org/docs/refs-and-the-dom.html#callback-refs) to the root element.
 
 Source: [ReactDOM documentation](https://facebook.github.io/react/docs/react-dom.html#render)
 

docs/rules/no-unused-prop-types.md

@@ -140,5 +140,5 @@ AComponent.propTypes = {
 ```
 
 [PropTypes]: https://reactjs.org/docs/typechecking-with-proptypes.html
-[TypeScript]: http://www.typescriptlang.org/
+[TypeScript]: https://www.typescriptlang.org/
 [Flow]: https://flow.org/

docs/rules/prefer-stateless-function.md

@@ -6,7 +6,7 @@ Stateless functional components are simpler than class based components and will
 
 This rule will check your class based React components for
 
-* methods/properties other than `displayName`, `propTypes`, `contextTypes`, `defaultProps`, `render` and useless constructor (same detection as `eslint` [no-useless-constructor rule](http://eslint.org/docs/rules/no-useless-constructor))
+* methods/properties other than `displayName`, `propTypes`, `contextTypes`, `defaultProps`, `render` and useless constructor (same detection as `eslint` [no-useless-constructor rule](https://eslint.org/docs/rules/no-useless-constructor))
 * instance property other than `this.props` and `this.context`
 * extension of `React.PureComponent` (if the `ignorePureComponents` flag is true)
 * presence of `ref` attribute in JSX