Removed version note.

dobooth · dobooth · commit 540a3b5570b9 · 2019-03-07T15:45:20.000-06:00
diff --git a/docs/commands/codeception.md b/docs/commands/codeception.md
@@ -1,6 +1,5 @@
 # CLI commands: vendor/bin/codecept
 
-<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
 
 <span class="bs-callout bs-callout-warning">
 We do not recommend using Codeception commands directly as they can break the MFTF basic workflow.
diff --git a/docs/commands/mftf.md b/docs/commands/mftf.md
@@ -169,7 +169,7 @@ The command that encodes this complex configuration:
 vendor/bin/mftf generate:tests --tests "{\r\n\"tests\":[\r\n\"general_test1\",\r\n\"general_test2\",\r\n\"general_test3\"\r\n],\r\n\"suites\":{\r\n\"sample\":[\r\n\"suite_test1\"\r\n],\r\n\"sample2\":null\r\n}\r\n}"
 ```
 
-Note: The strings must be escaped and surrounded in quotes.
+Note that the strings must be escaped and surrounded in quotes.
 
 ### `generate:suite`
 
diff --git a/docs/configuration.md b/docs/configuration.md
@@ -1,7 +1,5 @@
 # Configuration
 
-<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
-
 The `*.env` file provides additional configuration for the Magento Functional Testing Framework (MFTF).
 To run the MFTF on your Magento testing instance, specify the basic configuration values.
 Advanced users can create custom configurations based on requirements and environment.
diff --git a/docs/data.md b/docs/data.md
@@ -63,7 +63,9 @@ In this example:
 * `email` is a data key of the entity.
   The corresponding value will be assigned to `userInput` as a result.
 
-Note: As of MFTF 2.3.6, you no longer need to differentiate between scopes (a test, a hook, or a suite) for persisted data when referencing it in tests.
+<div class="bs-callout bs-callout-info">
+As of MFTF 2.3.6, you no longer need to differentiate between scopes (a test, a hook, or a suite) for persisted data when referencing it in tests.
+</div>
 
 The MFTF now stores the persisted data and attempts to retrieve it using the combination of `stepKey` and the scope of where it has been called.
 The current scope is preferred, then widening to _test > hook > suite_ or _hook > test > suite_.
diff --git a/docs/extending.md b/docs/extending.md
@@ -1,7 +1,5 @@
 # Extending
 
-<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
-
 There are cases when you need to create many tests that are very similar to each other.
 For example, only one or two parameters (for example, URL) might vary between tests.
 To avoid copy-pasting and to save some time the Magento Functional Testing Framework (MFTF) enables you to extend test components such as [test], [data], and [action group].
diff --git a/docs/getting-started.md b/docs/getting-started.md
@@ -1,7 +1,5 @@
 # Getting started
 
-<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
-
 <div class="bs-callout bs-callout-info">
 <a href="https://devdocs.magento.com/mftf/2.3/introduction.html#find-version">Find out your version</a> of the MFTF.
 
diff --git a/docs/introduction.md b/docs/introduction.md
@@ -1,7 +1,5 @@
 # Introduction to the Magento Functional Testing Framework version 2.3
 
-<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
-
 <a href="https://devdocs.magento.com/mftf/2.3/introduction.html#find-version">Find out your version</a> of the MFTF.
 
 The latest Magento 2.3 release supports MFTF 2.3.13.
@@ -134,4 +132,4 @@ Follow the [MFTF project] and [contribute on Github].
 <!-- Link definitions -->
 [contribute on Github]: https://github.com/magento/magento2-functional-testing-framework/blob/master/.github/CONTRIBUTING.md
 [Functional Testing Framework]: https://devdocs.magento.com/guides/v2.3/mtf/mtf_introduction.html
-[MFTF project]: https://github.com/magento/magento2-functional-testing-framework
+[MFTF project]: https://github.com/magento/magento2-functional-testing-framework
diff --git a/docs/merging.md b/docs/merging.md
@@ -1,7 +1,5 @@
 # Merging
 
-<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
-
 The MFTF allows you to merge test components defined in XML files, such as:
 
 - [`<tests>`][]
diff --git a/docs/metadata.md b/docs/metadata.md
@@ -1,7 +1,5 @@
 # Metadata
 
-<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
-
 In this topic we talk about handling entities that you need in your tests (such as categories, products, wish lists, and similar) using the MFTF.
 Using data handling actions like [`createData`], [`deleteData`], [`updateData`], and [`getData`], you are able to create, delete, update, and read entities for your tests.
 The framework enables you to send HTTP requests with these statically defined data entities:
@@ -183,8 +181,10 @@ The following is encoded in `<operation>`:
 The parameter that declares a body of the request is _catalogCategoryRepositoryV1SavePostBody_.
 Using the [Reference], we can trace how the JSON request was converted into XML representation.
 
-Note: Comments in the example below are used to demonstrate relation between JSON request and MFTF metadata in XML.
+<div class="bs-callout bs-callout-info">
+Comments in the example below are used to demonstrate relation between JSON request and MFTF metadata in XML.
 JSON does not support comments.
+</div>
 
 Model schema for _catalogCategoryRepositoryV1SavePostBody_ with XML representation of _Catalog/Metadata/category-meta.xml_ in comments:
 
diff --git a/docs/page.md b/docs/page.md
@@ -1,7 +1,5 @@
 # Page structure
 
-<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
-
 The MFTF uses a modified concept of [PageObjects], which models the testing areas of your page as objects within the code.
 This reduces occurrences of duplicated code and enables you to fix things quickly, in one place, when things change.
 You define the contents of a page, for reference in a [`<test>`], at both the [`<page>`] and [`<section>`] level.
diff --git a/docs/reporting.md b/docs/reporting.md
@@ -299,8 +299,10 @@ To launch the generated report in a web browser:
 allure open dev/tests/acceptance/tests/_output/allure-report
 ```
 
-Note: By default, Allure generates reports in the `allure-report/` at the current directory.
+<div class="bs-callout bs-callout-info">
+By default, Allure generates reports in the `allure-report/` at the current directory.
 For example, if you run the command without `-o` flag while you are in the `magento2/` directory, Allure will generate a report at the `magento2/allure-report/` directory.
+</div>
 
 ```bash
 allure generate dev/tests/acceptance/tests/_output/allure-result
diff --git a/docs/section.md b/docs/section.md
@@ -1,7 +1,5 @@
 # Section structure
 
-<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
-
 A `<section>` is a reusable part of a [`<page>`](./page.md) and is the standard file for defining UI elements on a page used in a test.
 
 A `<section>` can define:
diff --git a/docs/section/locator-functions.md b/docs/section/locator-functions.md
@@ -1,6 +1,5 @@
 # Locator functions
 
-<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
 
 ## Define Locator::functions in elements
 
diff --git a/docs/section/parameterized-selectors.md b/docs/section/parameterized-selectors.md
@@ -1,6 +1,5 @@
 # Parameterized selectors
 
-<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
 
 Use the following examples to create and use parameterized selectors in the MFTF.
 
diff --git a/docs/suite.md b/docs/suite.md
@@ -1,7 +1,5 @@
 # Suites
 
-<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
-
 Suites are essentially groups of tests that run in the specific conditions (preconditions and postconditions).
 They enable you including, excluding, and grouping tests for a customized test run when you need it.
 You can form suites using separate tests, groups, and modules.
@@ -10,7 +8,9 @@ Each suite must be defined in the `<magento 2 root>/dev/tests/acceptance/tests/_
 The generated tests for each suite go into a separate directory under `<magento 2 root>/dev/tests/acceptance/tests/functional/Magento/FunctionalTest/_generated/`.
 By default, all generated tests are stored in the _default_ suite under `.../Magento/FunctionalTest/_generated/default/`
 
-Note: If a test is generated into at least one custom suite, it will not appear in the _default_ suite.
+<div class="bs-callout bs-callout-info">
+ If a test is generated into at least one custom suite, it will not appear in the _default_ suite.
+</div>
 
 ## Format
 
@@ -216,8 +216,10 @@ A suite hook with preconditions that executes once before the suite tests.
 
 It may contain test steps with any [actions] and [action groups].
 
-Note: Tests in the suite are not run and screenshots are not saved in case of a failure in the before hook.
+<div class="bs-callout bs-callout-info">
+Tests in the suite are not run and screenshots are not saved in case of a failure in the before hook.
 To troubleshoot the failure, run the suite locally.
+</div>
 
 ### after {#after-tag}
 
diff --git a/docs/test.md b/docs/test.md
@@ -1,16 +1,16 @@
 # Test
 
-<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
-
 Test cases in the Magento Functional Testing Framework (MFTF) are defined in XML as [`<tests>`].
 `<tests>` is a [Codeception test container][Codeception] that contains multiple individual tests with test metadata and before and after actions.
 
 MFTF `<tests>` is considered a sequence of actions with associated parameters.
 Any failed [assertion] within a test constitutes a failed test.
 
-Note: `<before>` and `<after>` hooks are not global within `<tests>`.
+<div class="bs-callout bs-callout-info">
+ `<before>` and `<after>` hooks are not global within `<tests>`.
 They only apply to the `<test>` in which they are declared.
 The steps in `<after>` are run in both successful **and** failed test runs.
+</div>
 
 The following diagram shows the structure of an MFTF test case:
 
diff --git a/docs/test/actions.md b/docs/test/actions.md
@@ -1,6 +1,5 @@
 # Test actions
 
-<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
 
 Actions in the MFTF allow you to automate different scenarios of Magento user's actions.
 They are mostly XML implementations of [Codeception actions](http://codeception.com/docs/modules/WebDriver#Actions).
diff --git a/docs/test/annotations.md b/docs/test/annotations.md
@@ -1,6 +1,5 @@
 # Annotations
 
-<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
 
 Annotations are essentially comments in the code. In PHP, they all are marked by a preceding `@` symbol.
 
diff --git a/docs/test/assertions.md b/docs/test/assertions.md
@@ -1,6 +1,5 @@
 # Assertions
 
-<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
 
 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.
 
diff --git a/docs/tips-tricks.md b/docs/tips-tricks.md
@@ -1,7 +1,5 @@
 # Tips and Tricks
 
-<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
-
 Sometimes, little changes can make a big difference in your project. Here are some test writing tips to keep everything running smoothly.
 
 ## Actions and action groups
@@ -398,4 +396,5 @@ BAD:
 <click selector="{{ProductInWebsitesSection.website('Second Website')}}" stepKey="selectSecondWebsite"/>
 <click selector="{{ProductInWebsitesSection.website('Second Website')}}" stepKey="unselectSecondWebsite"/>
 ```
+
 <!--{% endraw %}-->
diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md
@@ -1,7 +1,5 @@
 # Troubleshooting
 
-<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
-
 Having a little trouble with the MFTF? See some common errors and fixes below.
 
 ## WebDriver issues
diff --git a/docs/update.md b/docs/update.md
@@ -1,7 +1,5 @@
 # Update the Magento Functional Testing Framework
 
-<span style="text-align: right">_This topic was updated due to the 2.3.13 MFTF release._</span>
-
 <div class="bs-callout bs-callout-info">
 <a href="https://devdocs.magento.com/mftf/2.3/introduction.html#find-version">Find out your version</a> of the MFTF.
 
diff --git a/docs/versioning.md b/docs/versioning.md
@@ -1,4 +1,4 @@
-# Versioning 
+# Versioning
 
 This documemt describes the versioning policy for the Magento Functional Testing Framework (MFTF), including the version numbering schema.
 
