Merge pull request #380 from WordPress-Coding-Standards/feature/versi…

…on-comment

Update comment about required phpcs version

README.md

@@ -31,7 +31,7 @@ For convenience of using `phpcs` as global command you might want to add path to
 
 1. Install PHP_CodeSniffer by following its [installation instructions](https://github.com/squizlabs/PHP_CodeSniffer#installation) (via Composer, PEAR, or Git checkout).
 
-  Do ensure, if for example you're using [VVV](https://github.com/Varying-Vagrant-Vagrants/VVV), that you have the **latest version** of CodeSniffer (earlier versions, e.g. ~1.5.5, may warn about incorrect line indentation on every single line even if your code is actually correct.)
+  Do ensure, if for example you're using [VVV](https://github.com/Varying-Vagrant-Vagrants/VVV), that PHP_CodeSniffer's version matches our requirements (you can check the required version in [composer.json](composer.json#L18)).
 
 2. Clone WordPress standards repository:
 

composer.json

@@ -2,12 +2,8 @@
 	"name"       : "wp-coding-standards/wpcs",
 	"description": "PHP_CodeSniffer rules (sniffs) to enforce WordPress coding conventions",
 	"keywords"   : ["phpcs", "standards", "WordPress"],
-    "license"    : "MIT",
+	"license"    : "MIT",
 	"authors"    : [
-		{
-			"name"    : "X-Team",
-			"homepage": "http://x-team.com/"
-		},
 		{
 			"name"    : "Contributors",
 			"homepage": "https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/graphs/contributors"
@@ -25,4 +21,4 @@
 		"post-install-cmd": "\"vendor/bin/phpcs\" --config-set installed_paths ../../..",
 		"post-update-cmd" : "\"vendor/bin/phpcs\" --config-set installed_paths ../../.."
 	}
-}
+}