Updated docs and configuration.

Author: DKravtsov

.idea/externalDependencies.xml

@@ -135,18 +135,18 @@ make phpcpd-html-report
 ```
 
 ### Composer tools
-To normalize or validate your composer.json you can use next local shell commands:
+To normalize or validate your composer.json, you can use next local shell commands:
 ```bash
 make composer-normalize
 make composer-validate
 ```
 
-If you need to find unused packages by scanning your code you can use next local shell commands:
+If you need to find unused packages by scanning your code, you can use next local shell commands:
 ```bash
 make composer-unused
 ```
 
-In order to check the defined dependencies against your code you can use next local shell commands:
+In order to check the defined dependencies against your code, you can use next local shell commands:
 ```bash
 make composer-require-checker
 ```
@@ -157,7 +157,7 @@ Use next local shell command in order to run it:
 ```bash
 make phpmetrics
 ```
-Note: You need run tests before this local shell command.
+Note: You need to run tests before this local shell command.
 
 After execution above local shell command please open `reports/phpmetrics/index.html` with your browser.
 
@@ -203,7 +203,7 @@ Please use next workflow for migrations:
 
 Above commands you can run in symfony container shell using next: `./bin/console doctrine:migrations:<command>`.
 
-Using above workflow allow you make database changes on your application.
+Using above workflow allows you make database changes on your application.
 Also you do not need to make any migrations files by hand (Doctrine will handle it).
 Please always check generated migration files to make sure that those doesn't contain anything that you really don't want.
 

.idea/php-test-framework.xml

@@ -1,5 +1,5 @@
 # Messenger
-This document describing how you can use [symfony/messenger](https://symfony.com/doc/current/messenger.html) bundle inside this environment.
+This document describing how you can use [symfony/messenger](https://symfony.com/doc/current/messenger.html) bundle.
 
 ## Basics
 

.idea/php.xml

@@ -4,22 +4,20 @@ This document describing how you can configure your IDE [PhpStorm](https://www.j
 ## Configuring PhpStorm
 ### General
 * Go to `Settings -> Plugins` and install next plugins:
-    - .env files support
     - .ignore
-    - Elasticsearch (Paid)
-    - Makefile Language
     - Php Annotations
     - Php Inspections (EA Extended)
     - Php Toolbox
-    - Symfony support (Has some paid functions, [homepage](https://espend.de/phpstorm/plugin/symfony))
-    - Rainbow brackets
+    - JetBrains AI Assistant
+    - Symfony Plugin (Has some paid functions, [homepage](https://espend.de/phpstorm/plugin/symfony))
+    - Rainbow Brackets
     - String Manipulation
-    - Extra ToolWindow Colorful Icons
+    - Elasticsearch (Paid)
 * Go to `Settings -> Php -> Symfony` and check `Enable plugin for this project` and set Web Directory value as `public`.
-* If you want control quality of your PHP project - pay your attention to the tools, described [here](development.md).
+* If you want to control quality of your PHP project - pay your attention to the tools, described [here](development.md).
 
 ### CLI Interpreter
-You need to set correct CLI interpreter for your PhpStorm.
+You need to set a correct CLI interpreter for your PhpStorm.
 In order to do it please open `Settings -> PHP` section and follow recommendations [configuring remote PHP interpreters](https://www.jetbrains.com/help/phpstorm/configuring-remote-interpreters.html).
 
 ![Path mappings](images/phpstorm_00.png)
@@ -37,7 +35,7 @@ You need to configure how your local files will be mapped inside docker containe
 ![Path mappings](images/phpstorm_03.png)
 
 ### Test Frameworks
-If you want to run tests directly from your IDE you need to do following configuration in `Settings -> PHP -> Test Frameworks`:
+If you want to run tests directly from your IDE you need to do a following configuration in `Settings -> PHP -> Test Frameworks`:
 
 ![Path mappings](images/phpstorm_04.png)
 
@@ -63,30 +61,30 @@ Anyway you can always import our recommended code style if you don't have commit
 ![Path mappings](images/phpstorm_php_code_sniffer_2.png)
 ![Path mappings](images/phpstorm_php_cs_fixer_1.png)
 
-Note: make sure that you have proper local path for the PHP CS Fixer ruleset `.php-cs-fixer.dist.php`.
+Note: make sure that you have a proper local path for the PHP CS Fixer ruleset `.php-cs-fixer.dist.php`.
 
 ![Path mappings](images/phpstorm_php_cs_fixer_2.png)
 ![Path mappings](images/phpstorm_phpstan_1.png)
 ![Path mappings](images/phpstorm_phpstan_2.png)
 ![Path mappings](images/phpstorm_phpmd_1.png)
 
-Note: make sure that you have proper local path for the MessDetector ruleset `phpmd_ruleset.xml`.
+Note: make sure that you have a proper local path for the MessDetector ruleset `phpmd_ruleset.xml`.
 
 ![Path mappings](images/phpstorm_phpmd_2.png)
 
 * If you don't have committed folder `.idea/`, go to `Settings -> Editor -> Inspections` and import profile `Project Default` (Inspections.xml) from [docs/phpstorm](phpstorm):
 
 ![Path mappings](images/phpstorm_inspections.png)
 
-* Go to `Settings -> Tools -> External tools` and create ecs tool:
+* Go to `Settings -> Tools -> External Tools` and create ecs tool:
 
 ![Path mappings](images/phpstorm_12.png)
 
 Note: Arguments value should be `exec-bash cmd="./vendor/bin/ecs --clear-cache check $FilePathRelativeToProjectRoot$"`.
 
 Note: In order to use it - right click on the necessary file/folder in PhpStorm and select context menu `External Tools -> ecs`.
 
-* Go to `Settings -> Tools -> External tools` and create phpcs tool:
+* Go to `Settings -> Tools -> External Tools` and create phpcs tool:
 
 ![Path mappings](images/phpstorm_13.png)
 
@@ -95,7 +93,7 @@ Note: Arguments value should be `exec-bash cmd="./vendor/bin/phpcs --version &&
 Note: In order to use it - right click on the necessary file/folder in PhpStorm and select context menu `External Tools -> phpcs`.
 
 
-For inspecting your code you can use main menu item `Code -> Inspect Code`. Code will be processed by code quality tools like PHP CS Fixer, PHP Mess Detector, PHP CodeSniffer, PHPStan. 
+For inspecting your code you can use main menu item `Code -> Inspect Code`. Code will be processed by code quality tools like PHP CS Fixer, PHP CodeSniffer, PHPStan, PHP Mess Detector. 
 
 ## External documentations
 * [Configuring Remote PHP Interpreters](https://www.jetbrains.com/help/phpstorm/configuring-remote-interpreters.html)

docs/development.md

@@ -1,10 +1,10 @@
 # Postman
-This document describing how you can use [Postman](https://www.getpostman.com/) within this environment.
+This document describing how you can use [Postman](https://www.getpostman.com/).
 
 ## Using Postman
 1. [Install Postman](https://www.getpostman.com/postman)
 2. [Import all files from "postman" folder](postman)
 3. Select `dev` environment in top right corner
-4. After getting token don't forget to update value for `token` variable in `manage environments` section in order to call protected entry points
+4. After getting token, don't forget to update value for `token` variable in the `manage environments` section in order to call protected entry points
 
 ![Using Postman](images/postman_01.png)

docs/images/phpstorm_01.png

@@ -1,5 +1,5 @@
 # Redis GUI
-This document describing how you can use [RedisInsight](https://redis.com/redis-enterprise/redis-insight/) within this environment.
+This document describing how you can use [RedisInsight](https://redis.com/redis-enterprise/redis-insight/).
 
 ## Using RedisInsight
 1. [Install RedisInsight](https://redis.com/redis-enterprise/redis-insight/) via your OS Application Manager or download via official web-site

docs/images/phpstorm_02.png

@@ -1,5 +1,5 @@
 # Swagger
-This document describing how you can use [Swagger](https://swagger.io/) within this environment.
+This document describing how you can use [Swagger](https://swagger.io/).
 
 ## Using Swagger
 * [Local Swagger service](http://localhost/api/doc) - Open next url http://localhost/api/doc in order to use Swagger.

docs/images/phpstorm_03.png

@@ -1,8 +1,8 @@
 # Testing
-This document describing how you can run tests within this environment.
+This document describing how you can run tests.
 
 ### General
-This environment contains next [types](https://symfony.com/doc/current/testing.html#types-of-tests) of tests:
+This environment contains the next [types](https://symfony.com/doc/current/testing.html#types-of-tests) of tests:
 
 * Application tests
 * Integration tests
@@ -15,14 +15,14 @@ Note 1: Please note that this environment does not use simple phpunit as does Sy
 Note 2: `Application` test === `Functional` test, please use naming convention(`Application`) as described [here](https://symfony.com/doc/current/testing.html#application-tests).
 
 ### Commands to run tests
-You can run tests using following local shell command(s):
+You can run tests using the following local shell command(s):
 ```bash
 make phpunit    # Run all tests
 ```
 
-After execution above local shell command you are able to check code coverage report. Please open `reports/coverage/index.html` with your browser.
+After execution above local shell command, you are able to check a code coverage report. Please open `reports/coverage/index.html` with your browser.
 
-If you want to run single test or all tests in specified directory you can use next steps:
+If you want to run a single test or all tests in specified directory, you can use the next steps:
 
 1.Use next local shell command in order to enter into symfony container shell:
 ```bash
@@ -31,23 +31,12 @@ make ssh    # Enter symfony container shell
 2.Use next symfony container shell command(s) in order to run test(s):
 ```bash
 ./vendor/bin/phpunit ./tests/Application/Controller/ApiKeyControllerTest.php  # Just this single test class
-./vendor/bin/phpunit ./tests/Application/Controller/                          # All tests in this directory
+./vendor/bin/phpunit ./tests/Application/Controller/                          # All tests in the directory
 ```
 
 ### Separate environment for testing
-By default this environment is using separate database for testing.
+By default, this environment is using a separate database for testing.
 If you need to change separate environment for testing (f.e. change database or another stuff) you need to edit `.env.test` file.
 
-
-## Metrics
-This environment contains [PhpMetrics](https://github.com/phpmetrics/phpmetrics) to make some code analysis.
-Use next local shell command in order to run it:
-```bash
-make phpmetrics
-```
-Note: You need run tests before this local shell command.
-
-After execution above local shell command please open `reports/phpmetrics/index.html` with your browser.
-
 ## PhpStorm
 You can run tests directly from your IDE PhpStorm. Please follow [PhpStorm](phpstorm.md) documentation in order to do it.