<span> to <div> since the latter is block element.

Author: dobooth

docs/commands/codeception.md

@@ -1,9 +1,9 @@
 # CLI commands: vendor/bin/codecept
 
 
-<span class="bs-callout bs-callout-warning">
+<div class="bs-callout bs-callout-warning">
 We do not recommend using Codeception commands directly as they can break the MFTF basic workflow.
-All the Codeception commands you need are wrapped using the [`mftf` tool][].</span>
+All the Codeception commands you need are wrapped using the [`mftf` tool][].</div>
 
 To run the Codeception testing framework commands directly, change your directory to the `<Magento root>`.
 
@@ -35,9 +35,9 @@ vendor/bin/codecept run functional --group example --skip-group skip
 vendor/bin/codecept run
 ```
 
-<span class="bs-callout .bs-callout-info"
+<div class="bs-callout .bs-callout-info">
 The following documentation corresponds to Codeception 2.3.8.
-</span>
+</div>
 
 ```bash
 Full reference:

docs/commands/mftf.md

@@ -1,7 +1,5 @@
 # CLI commands: vendor/bin/mftf
 
-<span class="style="text-align: right"">_This topic was updated due to the 2.3.13 MFTF release._</span>
-
 The Magento Functional Testing Framework (MFTF) introduces the command line interface (CLI) tool `vendor/bin/mftf` to facilitate your interaction with the framework.
 
 Note that `mftf` commands replace the `robo` commands that were used in previous releases.

docs/configuration.md

@@ -18,9 +18,9 @@ Example:
 MAGENTO_BASE_URL=http://magento2.vagrant251
 ```
 
-<span class=".bs-callout .bs-callout-info">
+<div class=".bs-callout .bs-callout-info">
 If the `MAGENTO_BASE_URL` contains a subdirectory (like `http://magento.test/magento2ce`), specify [`MAGENTO_CLI_COMMAND_PATH`][].
-</span>
+</div>
 
 ### MAGENTO_BACKEND_NAME
 
@@ -86,10 +86,10 @@ SELENIUM_PROTOCOL=http
 SELENIUM_PATH=/wd/hub
 ```
 
-<span class=".bs-callout .bs-callout-warning">
+<div class=".bs-callout .bs-callout-warning">
 `SELENIUM_*` values are required if you are running Selenium on an external system.
 If you change the configuration of the external Selenium server, you must update these values.
-</span>
+</div>
 
 #### SELENIUM_HOST
 

docs/credentials.md

@@ -89,8 +89,8 @@ The MFTF dynamically retrieves, encrypts, and decrypts the sensitive data during
 Decrypted credentials do not appear in the console, error logs, or [test reports][].
 The decrypted values are only available in the `.credentials` file.
 
-<span class=".bs-callout .bs-callout-info">
-The MFTF tests delivered with Magento application do not use credentials and do not cover external services, because of sensitivity of the data.</span>
+<div class=".bs-callout .bs-callout-info">
+The MFTF tests delivered with Magento application do not use credentials and do not cover external services, because of sensitivity of the data.</div>
 
 <!-- Link definitions -->
 [`fillField`]: test/actions.md#fillfield

docs/getting-started.md

@@ -68,9 +68,9 @@ To disable the WYSIWYG and enable the web driver to process these fields as simp
 3. In the WYSIWYG Options section set the **Enable WYSIWYG Editor** option to **Disabled Completely**.
 4. Click **Save Config**.
 
-<span class=".bs-callout .bs-callout-tip">
+<div class=".bs-callout .bs-callout-tip">
 When you want to test the WYSIWYG functionality, re-enable WYSIWYG in your test suite.
-</span>
+</div>
 
 ### Security settings   {#security-settings}
 
@@ -115,10 +115,10 @@ vendor/bin/mftf generate:urn-catalog --force .idea/
 
 See [`generate:urn-catalog`][] for more details.'
 
-<span class=".bs-callout .bs-callout-tip">
+<div class=".bs-callout .bs-callout-tip">
 You can simplify command entry by adding the  absolute  path to the `vendor/bin` directory path to your PATH environment variable.
 After adding the path, you can run `mftf` without having to include `vendor/bin`.
-</span>
+</div>
 
 ### Step 2. Edit environmental settings   {#environment-settings}
 

docs/introduction.md

@@ -15,10 +15,10 @@ MFTF improves:
 - **Maintainability** based on simple test creation and overall structure.
 
 Because MFTF tests are written in XML, you no longer need to learn PHP to write tests.
-<span class=".bs-callout .bs-callout-info">
+<div class=".bs-callout .bs-callout-info">
 We are actively developing functional tests.
 Refer to `<magento_root>/app/code/<vendor_name>/<module_name>/Test/Mftf/` for examples.
-</span>
+</div>
 
 ## Audience
 

docs/reporting.md

@@ -277,9 +277,9 @@ Each time you run tests, the MFTF appends an XML file with results at the `tests
 
 The official [Allure Test Report][] documentation is well-covered, so we'll list only the CLI commands that you would need for your day-to-day work.
 
-<span class=".bs-callout .bs-callout-info">
+<div class=".bs-callout .bs-callout-info">
 The following commands are relative to the Magento installation directory.
-</span>
+</div>
 
 To generate a report to the `allure-report/` at the current directory:
 

docs/section.md

@@ -14,10 +14,10 @@ A `<section>` can define:
 Substitutable values in the test can be of the following formats:
 
 - String literals (`stringLiteral`)
-- References to a [data entity](./data.md) (XML data from the corresponding `.../Data/*.xml`) such as `entityName.Field`.
+- References to a [data entity][] (XML data from the corresponding `.../Data/*.xml`) such as `entityName.Field`.
 - Persisted data:
-  - `$persistedCreateDataKey.field$` for data created in the scope of a [test](./test.md#test-tag) using the [`<createData>`](./test/actions.md#createdata) action with `stepKey="persistedCreateDataKey"`.
-  - `$$persistedCreateDataKey.field$$` for data created in [before](./test.md#before-tag) and [after](./test.md#after-tag) hooks. Even though `<before>`and `<after>` are nested inside a [test](./test.md#test-tag), persisted data is stored differently when it is done in a test hook. Therefore it must be accessed with a different notation.
+  - `$persistedCreateDataKey.field$` for data created in the scope of a [test][] using the [`<createData>`][] action with `stepKey="persistedCreateDataKey"`.
+  - `$$persistedCreateDataKey.field$$` for data created in [before][] and [after][] hooks. Even though `<before>`and `<after>` are nested inside a [test][], persisted data is stored differently when it is done in a test hook. Therefore it must be accessed with a different notation.
 
 The following diagram shows the XML structure of an MFTF section:
 
@@ -84,7 +84,7 @@ The following is an example of a call in test:
 
 ### section {#section-tag}
 
-`<section>` contains the sequence of UI elements in a section of a [page](./page.md).
+`<section>` contains the sequence of UI elements in a section of a [page][].
 
 Attributes|Type|Use|Description
 ---|---|---|---
@@ -93,16 +93,16 @@ Attributes|Type|Use|Description
 
 ### element {#element-tag}
 
-`<element>`is a UI element used in an [action](./test/actions.md).
+`<element>`is a UI element used in an [action][].
 
 Attributes|Type|Use|Description
 ---|---|---|---
 `name`|string|required|The element name; Must be alphanumeric.
 `type`|string|required|The type of the element. Possible values: `text`, `textarea`, `input`, `button`, `checkbox`, `radio`, `checkboxset`, `radioset`, `date`, `file`, `select`, `multiselect`, `wysiwyg`, `iframe`, `block`.
-`selector`|string|optional|[XPath](https://www.w3schools.com/xml/xpath_nodes.asp) or [CSS](https://www.w3schools.com/cssref/css_selectors.asp) selector of the element.
-`locatorFunction`|string|optional|[Locator function](./section/locator-functions.md) declaration to be used in lieu of a selector.
+`selector`|string|optional|[XPath][] or [CSS][] selector of the element.
+`locatorFunction`|string|optional|[Locator function][] declaration to be used in lieu of a selector.
 `timeout`|string|optional|The timeout after interaction with the element (in seconds). The default is _none_.
-`parameterized`|boolean|optional|Include and set to `true` if the `selector` for this element has parameters that need to be replaced for proper use. Learn more in [Parameterized selectors](./section/parameterized-selectors.md).
+`parameterized`|boolean|optional|Include and set to `true` if the `selector` for this element has parameters that need to be replaced for proper use. Learn more in [Parameterized selectors][].
 `remove`|boolean|optional|The default is `false`. Set to `true` to remove this element during parsing.
 
 #### `timeout` attribute {#timeout-attribute}
@@ -138,4 +138,15 @@ Whenever the `signIn` button is used in a test, the MFTF will add a 30 second `w
 
 <!-- Link definitions -->
 
-[waitForPageLoad]: test/actions.md#waitforpageload
+[waitForPageLoad]: test/actions.md#waitforpageload
+[data entity]: ./data.md
+[test]: ./test.md#test-tag
+[`<createData>`]: ./test/actions.md#createdata
+[before]: ./test.md#before-tag
+[after]: ./test.md#after-tag
+[page]: ./page.md
+[action]: ./test/actions.md
+[XPath]: https://www.w3schools.com/xml/xpath_nodes.asp
+[CSS]: https://www.w3schools.com/cssref/css_selectors.asp
+[Locator function]: ./section/locator-functions.md
+[Parameterized selectors]: ./section/parameterized-selectors.md

docs/section/parameterized-selectors.md

@@ -73,9 +73,9 @@ For the parameterized part of the selector, add `{{var1}}, {{var2}}, ..., {{varN
 </section>
 ```
 
-<span class="bs-callout .bs-callout-info">
+<div class="bs-callout .bs-callout-info">
 There is no need to use sequential variables like `{{var1}}`, `{{var2}}`. Parameterized replacement reads variables and maps them to the test call of the element sequentially from left to right, meaning you can use a selector like `#element .{{categoryId}} .{{productId}}`."
-</span>
+</div>
 
 ## Use a parameterized selector in a test
 

docs/test/actions.md

@@ -1349,8 +1349,8 @@ Note that the makeScreenshot action does not automatically add the screenshot to
 <makeScreenshot userInput="example" stepKey="screenshotPage"/>
 ```
 
-<span class=".bs-callout .bs-callout-info">
-This action does not add a screenshot to the Allure [report](../reporting.md).</span>
+<div class=".bs-callout .bs-callout-info">
+This action does not add a screenshot to the Allure [report](../reporting.md).</div>
 
 ### maximizeWindow
 
@@ -2474,9 +2474,9 @@ Attribute|Type|Use|Description
 
 Wait for all Magento loading overlays to disappear.
 
-<span class=".bs-callout .bs-callout-info">
+<div class=".bs-callout .bs-callout-info">
 The CSS class for loading masks is not used consistently throughout Magento.
-Therefore, this convenience function tries to wait for various specific selectors.</span>
+Therefore, this convenience function tries to wait for various specific selectors.</div>
 
 ```config
 # Wait for these classes to not be visible