added minor edits

Author: Dmitry Shevtsov

guides/v2.0/mtf/mtf_entities/mtf_block.md

@@ -10,8 +10,6 @@ github_link: mtf/mtf_entities/mtf_block.md
 
 <h2>Block</h2>
 
-<h3>Contents</h3>
-
 * TOC
 {:toc}
 
@@ -205,7 +203,7 @@ Let's see the [Customer Login]({{site.mage2000url}}app/code/Magento/Customer/Blo
 
 <a href="{{site.baseurl}}common/images/mtf_block_login_ui.png"><img src="{{site.baseurl}}common/images/mtf_block_login_ui.png" /></a>
 
-The mapping file for the block is stored in `magento2/dev/tests/functional/tests/app/Magento/Customer/Test/Block/Form/Login.xml`, along with the block.
+The mapping file for the block is stored in `<magento2>/dev/tests/functional/tests/app/Magento/Customer/Test/Block/Form/Login.xml`, along with the block.
 
 <img src="{{site.baseurl}}common/images/mtf_block_login_dir.png" />
 

guides/v2.0/mtf/mtf_entities/mtf_fixture-repo.md

@@ -10,8 +10,6 @@ github_link: mtf/mtf_entities/mtf_fixture-repo.md
 
 <h2>Fixture repository</h2>
 
-<h3>Contents</h3>
-
 * TOC
 {:toc}
 
@@ -441,7 +439,7 @@ The preceding is an example of repository merging. Using the approach from the e
 
 Credentials are stored in XML file specified in `phpunit.xml`.
 
-You can find a template for credentials in <a href="https://github.com/magento/magento2/blob/master/dev/tests/functional/credentials.xml.dist"><code>magento2/dev/tests/functional/credentials.xml.dist</code></a>.
+You can find a template for credentials in <a href="https://github.com/magento/magento2/blob/master/dev/tests/functional/credentials.xml.dist"><code>&lt;magento2&gt;/dev/tests/functional/credentials.xml.dist</code></a>.
 
 Credentials always should stay invisible for security reasons. The MTF implicitly pastes credentials during the test run only.
 There are two ways to paste credentials:

guides/v2.0/mtf/mtf_entities/mtf_fixture.md

@@ -8,9 +8,7 @@ menu_order: 1
 github_link: mtf/mtf_entities/mtf_fixture.md
 ---
 
-<h2>Fixture</h3>
-
-<h3 id="mtf_fixture_content">Contents</h3>
+<h2>Fixture</h2>
 
 * TOC
 {:toc}

guides/v2.0/mtf/mtf_entities/mtf_handler.md

@@ -10,8 +10,6 @@ github_link: mtf/mtf_entities/mtf_handler.md
 
 <h2>Handler</h2>
 
-<h3 id="mtf_handler_overview">Contents</h3>
-
 * TOC
 {:toc}
 
@@ -41,7 +39,7 @@ One fixture can have various handlers. When we create an entity in the test we d
 
 ### `config.xml` {#mtf_handler_configxml}
 
-The default configuration for handlers is set in <a href="{{site.mage2000url}}dev/tests/functional/etc/config.xml.dist"><code>magento2/dev/tests/functional/etc/config.xml.dist</code></a>.  Create a duplicate of the file, and keep both, but make changes to the new one, which is called `config.xml`:
+The default configuration for handlers is set in <a href="{{site.mage2000url}}dev/tests/functional/etc/config.xml.dist"><code>&lt;magento2&gt;/dev/tests/functional/etc/config.xml.dist</code></a>.  Create a duplicate of the file, and keep both, but make changes to the new one, which is called `config.xml`:
 
     cp config.xml.dist config.xml
 

guides/v2.0/mtf/mtf_entities/mtf_page.md

@@ -10,8 +10,6 @@ github_link: mtf/mtf_entities/mtf_page.md
 
 <h2>Page</h2>
 
-<h3>Contents</h3>
-
 * TOC
 {:toc}
 
@@ -101,7 +99,7 @@ The page will be opened as a concatenation of `app_backend_url` from `<magento2>
 
 Storefront page is recognizable by `area` assigned any value except `Adminhtml`, *and* `mca` doesn't have `http`. This type of page extends the [Mtf\Page\FrontendPage][] class.
 
-The page will be opened as concatenation of `app_frontend_url` from `magento2/dev/tests/functional/phpunit.xml` and [mca](#mca) link.
+The page will be opened as concatenation of `app_frontend_url` from `<magento2>/dev/tests/functional/phpunit.xml` and [mca](#mca) link.
 
 ### External page {#mtf_page_extern}
 

guides/v2.0/mtf/mtf_installation.md

@@ -9,7 +9,7 @@ menu_order: 2
 github_link: mtf/mtf_installation.md
 ---
 <h2>Preface</h2>
-Well, you are on the way to install the Magento testing Framework!
+Well, you are on the way to install the Magento Testing Framework!
 
 Follow the next three steps:
 
@@ -65,7 +65,7 @@ The Magento Testing Framework requires Composer, which downloads libraries defin
 <div class="bs-callout bs-callout-info" id="info">
   <p>If command failed, maybe <a href="https://getcomposer.org">Composer</a> hasn't been installed globally.<br/>
   Copy <code>composer.phar</code> to <code>/usr/local/bin/composer</code>.<br/>
-  To run it locally put <code>composer.phar</code> into directory, where <code>composer.json</code> file is located (that is, <code>magento2/dev/tests/functional/</code>).<br/>
+  To run it locally put <code>composer.phar</code> into directory, where <code>composer.json</code> file is located (that is, <code>&lt;magento2&gt;/dev/tests/functional/</code>).<br/>
 And run from this directory <code>php composer.phar install</code>.</p>
 </div>
 

guides/v2.0/mtf/mtf_quickstart/mtf_quickstart_config.md

@@ -44,7 +44,7 @@ For `name="credentials_file_path" ` set `value="<full_path_to_directory>"` (that
 ### Edit `config.xml` to configure Magento Testing Framework {#mtf_quickstart_config_configxml}
 
 <div class="bs-callout bs-callout-info" id="info">
-  <p>The default configuration is set in <a href="{{site.mage2000url}}dev/tests/functional/etc/config.xml.dist"><code>magento2/dev/tests/functional/etc/config.xml.dist</code></a>. It should be copied as <code>config.xml</code> for further changes.</p>
+  <p>The default configuration is set in <a href="{{site.mage2000url}}dev/tests/functional/etc/config.xml.dist"><code>&lt;magento2&gt;/dev/tests/functional/etc/config.xml.dist</code></a>. It should be copied as <code>config.xml</code> for further changes.</p>
 </div>
 
 Find `config.xml` in `<magento2>/dev/tests/functional/etc`, and open it in editor.

guides/v2.0/mtf/mtf_quickstart/mtf_quickstart_logs.md

@@ -14,7 +14,7 @@ redirect_from: /guides/v1.0/mtf/mtf_quickstart/mtf_quickstart_logs.html
 All failed tests are logged in `<magento2>/dev/tests/functional/var/log`.
 
 <div class="bs-callout bs-callout-tip">
-  <p>This path is set in <code>magento2/dev/tests/functional/phpunit.xml</code>, element <code>&lt;env name="basedir" value="&lt;path_to_directory&gt;" /&gt;</code>.</p>
+  <p>This path is set in <code>&lt;magento2&gt;/dev/tests/functional/phpunit.xml</code>, element <code>&lt;env name="basedir" value="&lt;path_to_directory&gt;" /&gt;</code>.</p>
 </div>
 
 All Magento errors are logged in `<magento2>/var/log`.

guides/v2.0/mtf/mtf_update.md

@@ -16,10 +16,10 @@ Two types of updates are available.
 -     <a href="#mtf_update_install">Install a new version of the Magento Testing Framework</a>
 
 <div class="bs-callout bs-callout-info" id="info">
-<p>Use this type of update if the version of the Magento Testing Framework in <code>magento2/dev/tests/functional/composer.json</code> and last version in <code>magento2/dev/tests/functional/vendor/magento/mtf/CHANGELOG.md</code> are different. For example, when you updated Magento.</p>
+<p>Use this type of update if the version of the Magento Testing Framework in <code>&lt;magento2&gt;/dev/tests/functional/composer.json</code> and last version in <code>&lt;magento2&gt;/dev/tests/functional/vendor/magento/mtf/CHANGELOG.md</code> are different. For example, when you updated Magento.</p>
 </div>
 
--    <a href="#mtf_update_depend">Update components from dependencies in <code>magento2/dev/tests/functional/composer.json</code></a>
+-    <a href="#mtf_update_depend">Update components from dependencies in <code>&lt;magento2&gt;/dev/tests/functional/composer.json</code></a>
 
 <div class="bs-callout bs-callout-info" id="info">
 <p>Use this type of update if you want to update dependent software from <code>composer.json</code>, or changed <code>composer.json</code> dependencies.</p>