DevDocs: Update documentation regarding Update process

Author: lbajsarowicz

docs/update.md

@@ -1,79 +1,48 @@
 # Update the Magento Functional Testing Framework
 
 <div class="bs-callout bs-callout-info" markdown="1">
-[Find your version][] of the MFTF.
 
-The latest Magento 2.3 release supports MFTF 2.3.13.
-The latest Magento 2.2 release supports MFTF 2.3.8.
-</div>
-
-Magento tests and the framework are stored in different repositories.
-
-Magento tests are stored in the same repository as the Magento code base.
-When you pull changes in the Magento code, you're potentially pulling corresponding tests as well.
-
-The MFTF is installed separately as a dependency using Composer.
-When pulling the latest Magento code, update the corresponding Composer dependencies in the `magento2` root directory.
-This ensures that the MFTF is up to date.
+Both Magento `2.2` and `2.3` supports MFTF `2.5.3` ([Find your version][] of the MFTF).
 
-## Update the MFTF from 2.3.x
-
-To update the MFTF to the latest patch:
-
-1. Verify that the Magento [WYSIWYG settings][] and [Security settings][] are set appropriately.
-1. Check details about backward incompatible changes in the [Changelog][] and update your new or customized tests.
-1. Get the latest framework version using Composer:
-
-   ```bash
-   composer update
-   ```
-
-1. Generate the updated tests:
-
-   ```bash
-   vendor/bin/mftf generate:tests
-   ```
-
-## Update the MFTF from 2.2
+</div>
 
-To update the MFTF from the previous minor version:
 
-1. When you update Magento, verify that the Magento [WYSIWYG settings][] and [Security settings][] are set appropriately.
-1. Starting at the `magento2/` root directory remove the `vendor/` directory:
+**Tests and the Framework itself are stored in different repositories.**
 
-   ```bash
-   rm -rf vendor/
-   ```
+* Tests are stored in Module's directory.
+* The MFTF is installed separately (usually as a Composer dependency)
 
-1. Get the latest framework version from the Composer dependencies:
+While pulling the latest Magento codebase, you are going to get Tests and it's dependencies (eg. Action Groups).
 
-   ```bash
-   composer install
-   ```
+To understand types of update - please follow the [Versioning][] page. 
 
-1. Run the `upgrade:tests` using the new command line tool:
+## Patch version update
 
-   ```bash
-   vendor/bin/mftf upgrade:tests app
-   ```
+Takes place when **third** digit of version number changes.
 
-1. If you are using Phpstorm, update the urn catalog:
+1. Make sure that [Security settings][] are set appropriately.
+1. Get latest Framework version with `composer update magento/magento2-functional-testing-framework --with-dependencies`
+1. Generate updated tests with `vendor/bin/mftf generate:tests`
 
-   ```bash
-   vendor/bin/mftf generate:urn-catalog .idea/
-   ```
+## Minor version update
 
-1. Update your own tests, including data, metadata, and so on, if they contain tags that are unsupported in the newer version.
+Takes place when **second** digit of version number changes.
 
-   Check details about backward incompatible changes and review new MFTF release documentation in the [Changelog][].
+1. Check details about backward incompatible changes in the [Changelog][] and update your new or customized tests.
+1. Perform all the actions provided for [Patch Version Update][]
+1. When updating from versions below `2.5.0`, verify [WYSIWYG settings][]
+1. You may need to run the `upgrade:tests` using `vendor/bin/mftf upgrade:tests app`
 
-1. Generate newly pulled tests:
+## Always after update
 
-   ```bash
-   vendor/bin/mftf generate:tests
-   ```
+1. It's good to regenerate your IDE Schema Definition catalog with `vendor/bin/mftf generate:urn-catalog .idea/`
+1. Update your own tests, including data, metadata and other resoruces. Validate if they contain tags that are unsupported in the newer version.
+1. As soon as possible - remove the references to resources (ActionGroups, Sections, Tests) marked as deprecated.
 
 <!-- Link Definitions -->
 [Changelog]: https://github.com/magento/magento2-functional-testing-framework/blob/master/CHANGELOG.md
 [WYSIWYG settings]: getting-started.md#wysiwyg-settings
 [Security settings]: getting-started.md#security-settings
+[Find your version]: introduction.md#find-your-mftf-version
+[Versioning]: versioning.md#versioning-policy
+[Patch Version Update]: #patch-version-update