Readme: Better wording & fixed anchor link

README.md

@@ -4,48 +4,48 @@ This is a Flex pack to install multiple dev tools.
 
 ## Why
 
-On symfony, we create a project rapidly using composer :
+On Symfony, we create a project rapidly using composer :
 
 ```bash
 composer create-project symfony/skeleton
 ```
 
 After, we just have to require some [pack dependencies](http://fabien.potencier.org/symfony4-unpack-the-packs.html), and thanks to [flex](https://github.com/symfony/flex), all is configured.
 
-But, for some time, when I start a new project, I add dev-dependencies to improve code quality and keep it in the long run, so I regrouped them in this pack with pre-configured files.
+But, for some time, when I start a new project, I add dev-dependencies to improve code quality and keep it in the long run, so I grouped them in this pack with pre-configured files.
 
-It's allow me to have clean codes rules to share with project team, and avoid useless discussion in Code Reviews.
+It allows me to have clean codes rules to share with project team, and avoid useless discussion in Code Reviews.
 
 ![When using tabs instead space](https://ljdchost.com/vEKPc7F.gif)
 
 ## Installation and usage
 
-For this following, I assume you just freshly created a new Symfony Project.
+For the following, I assume you just freshly created a new Symfony Project.
 
 Require the pack as dev dependency
 
 ```bash
 composer require --dev barth/dev-pack
 ```
 
-You now have [my list of dev tools](#list-of-installed-package), with preconfigured files.
-Don't hesitate to alterate by your settings or feel free to fork this repo to have your own list and settings.
+You now have [my list of dev tools](#list-of-installed-packages), with preconfigured files.
+Don't hesitate to alterate with your settings or feel free to fork this repo to have your own list and settings.
 
 ## Cleaning / Unpack
 
-Because it's a **symfony-pack**, you may want to unpack it to keep only required dependency and no more **barth/dev-pack** in your **composer.json**.
+Because it's a **symfony-pack**, you may want to unpack it to keep only required dependencies and no more **barth/dev-pack** in your **composer.json**.
 
 :warning: I don't recommand to require this pack direclty with the **--unpack** flex option.
-If you do this, you don't have the preconfigured files.
+If you do this, you won't have the preconfigured files.
 
-To do this properly, unpack it after require it :
+To do this properly, unpack it after install:
 
 ```bash
 composer unpack barth/dev-pack
 ```
 
 Then, you can also remove [endroid/installer](https://github.com/endroid/installer)
-who provide a composer plugin to copy file from my pack.
+which provides a composer plugin to copy file from my pack.
 
 ```bash
 composer remove --dev endroid/installer
@@ -55,16 +55,16 @@ composer remove --dev endroid/installer
 
 ### [PHP CodeSniffer](https://github.com/squizlabs/PHP_CodeSniffer)
 
-This is the most well-known tool in the PHP community, configured with PSR2 ruleset
+This is the most well-known tool in the PHP community, configured with PSR2 ruleset.
 
 ### [PHPMD - Mess Detector](https://phpmd.org/)
 
-This tool focuses on the form of the code
-Here are the different rules it imposes:
+This tool focuses on the form of the code.
+Here are the different rules it enforces:
 
 - [Clean Code Rules](https://phpmd.org/rules/index.html#clean-code-rules): Do not pass a boolean as a parameter of a function, avoid `else` and access in` static`.
 - [Code Size Rules](https://phpmd.org/rules/index.html#code-size-rules): A class too long, a method that takes too much parameter, a function too complicated, it's here that it happens.
-- [Controversial Rules](https://phpmd.org/rules/index.html#controversial-rules): Controversial rules .. They focus on naming, especially through the use of CamelCase.
+- [Controversial Rules](https://phpmd.org/rules/index.html#controversial-rules): Controversial rules... They focus on naming, especially through the use of CamelCase.
 - [Design Rules](https://phpmd.org/rules/index.html#design-rules): A collection of rules that detect problems with software design.
 - [Naming Rules](https://phpmd.org/rules/index.html#naming-rules): Rules on names of variables, methods, classes - too long, too short, etc.
 - [Unused Code Rules](https://phpmd.org/rules/index.html#unused-code-rules): Detects unused pieces of code.
@@ -75,25 +75,25 @@ This tool prevents potential bugs before even executing the code. You can see [l
 
 ### [Sensio Security Checker](https://github.com/sensiolabs/security-checker)
 
-This tool will not avoid us (or very little) return code reviews, but ensures that our dependencies installed via [composer](https://getcomposer.org) do not contain known security vulnerabilities .
+This tool will not avoid us (or very little) return code reviews, but ensures that our dependencies installed via [composer](https://getcomposer.org) do not contain known security vulnerabilities.
 
 ### [PHPCPD - Copy / Paste Detector](https://github.com/sebastianbergmann/phpcpd)
 
-Very useful to refactor its code and avoid having identical pieces of code in several places of a project.
+Very useful to refactor code and avoid having identical pieces of code in several places of a project.
 
 ### [PHP-CS-Fixer](https://github.com/FriendsOfPHP/PHP-CS-Fixer)
 
 Similar to PHP CodeSniffer, it offers in my opinion a simpler configuration, and fixes errors in a command line.
 
 ### [GrumPHP](https://github.com/phpro/grumphp)
 
-Allow to orchestrate all these tools on the precommit hook.
+Allows to orchestrate all these tools on the precommit hook.
 
 ## Contribute
 
 First of all, thank you for contributing :heart:
 
-Keep in mind that if you add tools, I certainly accept only if fit with my own needs.
+Keep in mind that if you add tools, I certainly accept only if fits with my own needs.
 Don't hesitate to fork this project to fit with your organization needs.
 
 ## License