MQE-1796: Magento Git vs Composer and MFTF

Addressed review comments

Author: soumyau

docs/guides/git-vs-composer-install.md

@@ -5,7 +5,8 @@
 
 If you are planning on contributing a PR to the Magento 2 codebase, you can download Magento 2 from GitHub. Contribution to the codebase is done using the 'fork and pull' model where contributors maintain their own fork of the repo. This repo is then used to submit a pull request to the base repo.
 
-Install guide: [GitHub Installation](https://devdocs.magento.com/mftf/docs/getting-started.html)
+Install guide: [GitHub Installation](https://devdocs.magento.com/guides/v2.3/install-gde/prereq/dev_install.html)
+
 
 ###Composer based Installation
 
@@ -16,6 +17,13 @@ All Magento modules and their MFTF tests are put under `<vendor>` directory for
 Install guide: [Composer based Installation](https://devdocs.magento.com/guides/v2.3/install-gde/composer.html)
 
 
+### MFTF Installation
+
+After installing your Magento project in either of the above ways, the composer dependency `magento/magento2-functional-testing-framework` allows you to download and install MFTF. MFTF will be embedded in your Magento 2 installation and will cover your project with functional tests.  
+
+If you want to contribute a PR into MFTF codebase, you will need to install MFTF in the [Standalone] mode.
+
+
 ###Managing modules - Composer vs GitHub
 
 ####Via GitHub:
@@ -55,18 +63,22 @@ The file structure under both paths is the same as below:
     └── ...
 ```
 
+
 ###How ModuleResolver reads modules
 
 In either of the installations, all tests and test data are read and merged by MFTF's ModuleResolver in the order indicated below:
 
 1. `<magento_root>/app/code/<vendor_name>/<module_name>/Test/Mftf/`
 2. `<magento_root>/vendor/<vendor_name>/<module_name>/Test/Mftf/`
 
+
 ###Conclusion
 
 There are no differences from MFTF's perspective between having the test artifacts in `app/code` or in `/vendor` as it reads artifacts from both paths. It works the same. Composer based install may benefit teams when there's a need to match file systems in dev and production.
 
 If you are a contributing developer with an understanding of Git and Composer commands, you can choose the GitHub installation method instead.
 
 
+<!-- Link definitions -->
 
+[Standalone]: ../getting-started.html#set-up-a-standalone-mftf