`](../test.md#test-tag).
* Naming should be as descriptive as possible:
* Describe the action performed.
* Briefly describe the purpose.
@@ -166,18 +166,18 @@ The following test actions return a variable:
* [grabValueFrom](#grabvaluefrom)
* [executeJS](#executejs)
-Learn more in [Using data returned by test actions](../data.html#use-data-returned-by-test-actions).
+Learn more in [Using data returned by test actions](../data.md#use-data-returned-by-test-actions).
## Actions handling data entities
-The following test actions handle data entities using [metadata](../metadata.html):
+The following test actions handle data entities using [metadata](../metadata.md):
* [createData](#createdata)
* [deleteData](#deletedata)
* [updateData](#updatedata)
* [getData](#getdata)
-Learn more in [Handling a REST API response](../metadata.html#rest-response).
+Learn more in [Handling a REST API response](../metadata.md#rest-response).
## Reference
@@ -538,7 +538,7 @@ Attribute|Type|Use|Description
### createData
Creates an entity (for example, a category or product).
-To create an entity, the MFTF makes a `POST` request to the Magento API according to the [data](../data.html) and [metadata](../metadata.html) of the entity to be created.
+To create an entity, the MFTF makes a `POST` request to the Magento API according to the [data](../data.md) and [metadata](../metadata.md) of the entity to be created.
Attribute|Type|Use|Description
---|---|---|---
@@ -617,7 +617,7 @@ Attribute|Type|Use|Description
#### Examples
-Delete the entity that was previously created using [`createData`](#createdata) in the scope of the [test](../test.html#test-tag).
+Delete the entity that was previously created using [`createData`](#createdata) in the scope of the [test](../test.md#test-tag).
1. Create _SampleCategory_:
@@ -1127,7 +1127,7 @@ Attribute|Type|Use|Description
```
-The `ProductAttributeOptionGetter` entity must be defined in the corresponding [data `*.xml`](../data.html).
+The `ProductAttributeOptionGetter` entity must be defined in the corresponding [data `*.xml`](../data.md).
This action can optionally contain one or more [requiredEntity](#requiredentity) child elements.
@@ -1348,7 +1348,7 @@ Note that the makeScreenshot action does not automatically add the screenshot to
```
-This action does not add a screenshot to the Allure [report](../reporting.html).
+This action does not add a screenshot to the Allure [report](../reporting.md).
### maximizeWindow
diff --git a/docs/test/annotations.md b/docs/test/annotations.md
index d46cf221f..f30b8104e 100644
--- a/docs/test/annotations.md
+++ b/docs/test/annotations.md
@@ -227,7 +227,7 @@ Attribute|Type|Use
[setup instructions in Allure]: https://github.com/allure-framework/allure1/wiki/Test-Case-ID
[severity]: #severity
[stories]: #stories
-[suite]: ../suite.html
-[tests]: ../test.html
+[suite]: ../suite.md
+[tests]: ../test.md
[title]: #title
[skip]: #skip
diff --git a/docs/test/assertions.md b/docs/test/assertions.md
index 6a933c73f..17a3d194a 100644
--- a/docs/test/assertions.md
+++ b/docs/test/assertions.md
@@ -1,15 +1,15 @@
# Assertions
-Assertions serve to pass or fail the [test](../test.html#test-tag) if a condition is not met. These assertions will look familiar to you if you've used any other testing framework, like PHPUnit.
+Assertions serve to pass or fail the [test](../test.md#test-tag) if a condition is not met. These assertions will look familiar to you if you've used any other testing framework, like PHPUnit.
-All assertions contain the same [common actions attributes](./actions.html#common-attributes): `stepKey`, `before`, and `after`.
+All assertions contain the same [common actions attributes](./actions.md#common-attributes): `stepKey`, `before`, and `after`.
Most assertions contain a `message` attribute that specifies the text of an informational message to help you identify the cause of the failure.
## Principles
-The [principles for actions](../test.html#principles) are also applicable to assertions.
+The [principles for actions](../test.md#principles) are also applicable to assertions.
Assertion actions have nested self-descriptive elements, `` and ``. These elements contain a result type and a value:
diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md
index dd392827e..6ad300428 100644
--- a/docs/troubleshooting.md
+++ b/docs/troubleshooting.md
@@ -21,7 +21,7 @@ Use of PhantomJS is not actually supported by the MFTF.
#### Solution
-For headless browsing, the [Headless Chrome][]{:target="_blank"} has better compatibility with the MFTF.
+For headless browsing, the [Headless Chrome][]{:target="\_blank"} has better compatibility with the MFTF.
### Chrome
@@ -41,7 +41,7 @@ Chrome v62 is in the process of being rolled out, and it causes an error with Ch
#### Solution
-Use [ChromeDriver v2.33+][]{:target="_blank"} and [Selenium Server Standalone v3.6.0+][]{:target="_blank"} in order to execute tests in Google Chrome v62+.
+Use [ChromeDriver v2.33+][]{:target="\_blank"} and [Selenium Server Standalone v3.6.0+][]{:target="\_blank"} in order to execute tests in Google Chrome v62+.
### Firefox
diff --git a/docs/update.md b/docs/update.md
index 3a32492f2..1a3137eb6 100644
--- a/docs/update.md
+++ b/docs/update.md
@@ -75,6 +75,6 @@ To update the MFTF from the previous minor version:
[Changelog]: https://github.com/magento/magento2-functional-testing-framework/blob/master/CHANGELOG.md
-[WYSIWYG settings]: getting-started.html#wysiwyg-settings
-[Security settings]: getting-started.html#security-settings
-[Find your version]: introduction.html#find-your-mftf-version
\ No newline at end of file
+[WYSIWYG settings]: getting-started.md#wysiwyg-settings
+[Security settings]: getting-started.md#security-settings
+[Find your version]: introduction.md#find-your-mftf-version
\ No newline at end of file