MQE-1796: Magento Git vs Composer and MFTF

Addressed review comments

Author: soumyau

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

@@ -1,14 +1,14 @@
-#Git vs Composer Installation of Magento with MFTF
+# Git vs Composer Installation of Magento with MFTF
 
 
-###GitHub Installation
+### GitHub Installation
 
 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/guides/v2.3/install-gde/prereq/dev_install.html)
 
 
-###Composer based Installation
+### Composer based Installation
 
 Composer install downloads released packages of Magento 2 from the composer repo [https://repo.magento.com](https://repo.magento.com).
 
@@ -24,13 +24,13 @@ After installing your Magento project in either of the above ways, the composer
 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
+### Managing modules - Composer vs GitHub
 
-####Via GitHub:
+#### Via GitHub:
 
 Cloning Magento 2 git repository is a way of installing when you don't have to worry frequently about matching the codebase with production. Your version control system generally holds and manages your `app/code` folder and you can do manual ad-hoc development here.
 
-####Via composer:
+#### Via composer:
 
 Magento 2 advocates the use of composer for managing modules. When you install a module through composer, it is added to `vendor/<vendor-name>/<module>`
 
@@ -39,11 +39,11 @@ If you are developing your own module or adding MFTF tests to the module, you sh
 If you want to distribute the module and its tests, you can initialize a git repo and create a [composer package](https://devdocs.magento.com/guides/v2.3/extension-dev-guide/package/package_module.html). In this way others will be able to download and install your module and access your tests as a composer package, in their `<vendor>` folder.
 
 
-###MFTF test artifacts location
+### MFTF test artifacts location
 
-- For GitHub installation, MFTF test artifacts are located at `<magento_root>/app/code/<vendor_name>/<module_name>/Test/Mftf/`. This is the directory to create new tests or maintain existing ones.
+- For GitHub installation, MFTF test materials are located at `<magento_root>/app/code/<vendor_name>/<module_name>/Test/Mftf/`. This is the directory to create new tests or maintain existing ones.
 
-- For Composer based installation, MFTF test artifacts are located at `<magento_root>/vendor/<vendor_name>/<module_name>/Test/Mftf/`. This is the directory to run tests fetched by Composer.
+- For Composer based installation, MFTF test materials are located at `<magento_root>/vendor/<vendor_name>/<module_name>/Test/Mftf/`. This is the directory to run tests fetched by Composer.
 
 The file structure under both paths is the same as below:
 
@@ -64,17 +64,17 @@ The file structure under both paths is the same as below:
 ```
 
 
-###How ModuleResolver reads modules
+### 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
+### 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.
+There are no differences from MFTF's perspective between having the test materials 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.