diff --git a/wiki/Configuration-Options.md b/wiki/Configuration-Options.md
index 5e900e2..2b83804 100644
--- a/wiki/Configuration-Options.md
+++ b/wiki/Configuration-Options.md
@@ -243,7 +243,7 @@ $ phpcs --config-set ignore_non_auto_fixable_on_exit 1
 
 ### Setting the path to PHP
 
-The `Generic.PHP.Syntax` sniff will check the syntax of each PHP file using [the built-in PHP linter](http://php.net/manual/en/features.commandline.options.php). Use the `php_path` configuration option to tell the Syntax sniff where to find the PHP binary.
+The `Generic.PHP.Syntax` sniff will check the syntax of each PHP file using [the built-in PHP linter](https://www.php.net/commandline.options). Use the `php_path` configuration option to tell the Syntax sniff where to find the PHP binary.
 
 ```bash
 $ phpcs --config-set php_path /path/to/php
@@ -251,7 +251,7 @@ $ phpcs --config-set php_path /path/to/php
 
 ### Setting the path to CSSLint (PHP_CodeSniffer < 4.0.0)
 
-The `Generic.Debug.CSSLint` sniff will check each CSS file using [CSS Lint](http://csslint.net/). Use the `csslint_path` configuration option to tell the CSSLint sniff where to find the tool.
+The `Generic.Debug.CSSLint` sniff will check each CSS file using [CSS Lint](https://csslint.net/). Use the `csslint_path` configuration option to tell the CSSLint sniff where to find the tool.
 
 ```bash
 $ phpcs --config-set csslint_path /path/to/csslint
@@ -267,7 +267,7 @@ $ phpcs --config-set gjslint_path /path/to/gjslint
 
 ### Setting the path to JSHint (PHP_CodeSniffer < 4.0.0)
 
-The `Generic.Debug.JSHint` sniff will check each JavaScript file using [JSHint](http://www.jshint.com/), a tool to detect errors and potential problems in JavaScript code. Use the `jshint_path` configuration option to tell the JSHint sniff where to find the tool.
+The `Generic.Debug.JSHint` sniff will check each JavaScript file using [JSHint](https://jshint.com/), a tool to detect errors and potential problems in JavaScript code. Use the `jshint_path` configuration option to tell the JSHint sniff where to find the tool.
 
 ```bash
 $ phpcs --config-set jshint_path /path/to/jshint.js
@@ -281,7 +281,7 @@ $ phpcs --config-set rhino_path /path/to/rhino
 
 ### Setting the path to JSLint (PHP_CodeSniffer < 4.0.0)
 
-The `Squiz.Debug.JSLint` sniff will check each JavaScript file using [JSLint](http://www.jslint.com/), a JavaScript program that looks for problems in JavaScript programs. Use the `jslint_path` configuration option to tell the JSLint sniff where to find the tool.
+The `Squiz.Debug.JSLint` sniff will check each JavaScript file using [JSLint](https://www.jslint.com/), a JavaScript program that looks for problems in JavaScript programs. Use the `jslint_path` configuration option to tell the JSLint sniff where to find the tool.
 
 ```bash
 $ phpcs --config-set jslint_path /path/to/jslint.js
diff --git a/wiki/FAQ.md b/wiki/FAQ.md
index 0b55f5a..6971822 100644
--- a/wiki/FAQ.md
+++ b/wiki/FAQ.md
@@ -55,6 +55,6 @@ Always run PHP_CodeSniffer until you get a passing result. Once you've made the
 
 ## What does PHP_CodeSniffer use to tokenize my code?
 
-PHP_CodeSniffer uses [PHP's inbuilt tokenizer functions](http://www.php.net/tokenizer) to parse your code. It then modifies that output to include much more data about the file, such as matching function braces to function keywords.
+PHP_CodeSniffer uses [PHP's inbuilt tokenizer functions](https://www.php.net/tokenizer) to parse your code. It then modifies that output to include much more data about the file, such as matching function braces to function keywords.
 
 <p align="right"><a href="#table-of-contents">back to top</a></p>
diff --git a/wiki/Reporting.md b/wiki/Reporting.md
index 2ae00a5..142cbbd 100644
--- a/wiki/Reporting.md
+++ b/wiki/Reporting.md
@@ -211,7 +211,7 @@ patching file /path/to/code/fileB.php
 ```
 
 > [!NOTE]
-> The `*nix` `diff` command is required for generating reports in `diff` format. Windows users may need to ensure that the `diff` command is available by either installing [DiffUtils](http://gnuwin32.sourceforge.net/packages/diffutils.htm) or, if available, adding the Git `/usr/bin/` sub-directory to the Windows system `PATH`.
+> The `*nix` `diff` command is required for generating reports in `diff` format. Windows users may need to ensure that the `diff` command is available by either installing [DiffUtils](https://gnuwin32.sourceforge.net/packages/diffutils.htm) or, if available, adding the Git `/usr/bin/` sub-directory to the Windows system `PATH`.
 
 <p align="right"><a href="#table-of-contents">back to top</a></p>