Skip to content

Commit 34d33ec

Browse files
committed
Wiki: use HTTPS links
... in various places where the current URLs were redirecting to their HTTPS counterparts.
1 parent e1920ad commit 34d33ec

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

wiki/Configuration-Options.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -243,15 +243,15 @@ $ phpcs --config-set ignore_non_auto_fixable_on_exit 1
243243
244244
### Setting the path to PHP
245245
246-
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.
246+
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.
247247
248248
```bash
249249
$ phpcs --config-set php_path /path/to/php
250250
```
251251
252252
### Setting the path to CSSLint (PHP_CodeSniffer < 4.0.0)
253253
254-
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.
254+
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.
255255
256256
```bash
257257
$ phpcs --config-set csslint_path /path/to/csslint
@@ -267,7 +267,7 @@ $ phpcs --config-set gjslint_path /path/to/gjslint
267267
268268
### Setting the path to JSHint (PHP_CodeSniffer < 4.0.0)
269269
270-
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.
270+
The `Generic.Debug.JSHint` sniff will check each JavaScript file using [JSHint](https://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.
271271
272272
```bash
273273
$ phpcs --config-set jshint_path /path/to/jshint.js
@@ -281,7 +281,7 @@ $ phpcs --config-set rhino_path /path/to/rhino
281281
282282
### Setting the path to JSLint (PHP_CodeSniffer < 4.0.0)
283283
284-
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.
284+
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.
285285
286286
```bash
287287
$ phpcs --config-set jslint_path /path/to/jslint.js

wiki/FAQ.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,6 +55,6 @@ Always run PHP_CodeSniffer until you get a passing result. Once you've made the
5555

5656
## What does PHP_CodeSniffer use to tokenize my code?
5757

58-
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.
58+
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.
5959

6060
<p align="right"><a href="#table-of-contents">back to top</a></p>

wiki/Reporting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -211,7 +211,7 @@ patching file /path/to/code/fileB.php
211211
```
212212

213213
> [!NOTE]
214-
> 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`.
214+
> 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`.
215215
216216
<p align="right"><a href="#table-of-contents">back to top</a></p>
217217

0 commit comments

Comments
 (0)