MQE-1963: Update XSD Schema to verify that file has only single entity

- CR Fixes

Author: KevinBKozan

CHANGELOG.md

@@ -6,12 +6,12 @@ Magento Functional Testing Framework Changelog
 * Run `bin/mftf reset --hard` to remove old generated configurations.
 * Run `bin/mftf build:project` to generate new configurations.
 * Run `bin/mftf upgrade:tests`. [See command page for details](./docs/commands/mftf.md#upgradetests).
-* After running the above command, you will need to manually update some tests:
+* After running the above command, some tests may need manually updates:
     * Remove all occurrences of `<executeInSelenium>` and `<performOn>`
     * Remove all occurrences of `<module file=""/>` from any `<suite>`s
-    * Ensure all `<assert*>` actions in your tests do not have invalid schema
+    * Ensure all `<assert*>` actions in your tests have a valid schema.
 * Lastly, try to generate all tests. Tests should all be generated as a result of the upgrades.
-    If not, the most likely issue will be changed XML schema. You will need to check error messaging and search your codebase for the attributes listed.
+    * If not, the most likely issue will be a changed XML schema. Check error messaging and search your codebase for the attributes listed.
 
 2.6.3
 -----

docs/commands/mftf.md

@@ -479,7 +479,7 @@ Otherwise, it will apply all the major version MFTF upgrade scripts to all insta
 
 **Note**:
 
-The upgrade scripts are meant to be used for Test Modules under source code control. However, if you have old version of test modules under `vendor`, those test modules will get upgraded.
+The upgrade scripts are meant to be used for Test Modules under source code control. If you have old versions of test modules under vendor, those test modules will get upgraded
 
 #### Usage
 

docs/introduction.md

@@ -107,11 +107,11 @@ codeception.dist.yml            // Codeception configuration (generated while ru
 The MFTF supports three different locations for storing the tests and test artifacts:
 -  `<magento_root>/app/code/<vendor_name>/<module_name>/Test/Mftf/` is the directory to create new tests.
 -  `<magento_root>/vendor/<vendor_name>/<module_name>/Test/Mftf/` is the directory with the out of the box tests (fetched by the Composer).
--  `<magento_root>/dev/tests/acceptance/tests/functional/<vendor_name>/<module_name>/` is the directory to create new tests that depends on more than one Magento modules.
+-  `<magento_root>/dev/tests/acceptance/tests/functional/<vendor_name>/<module_name>/` is used to store tests that depend on multiple modules.
 
 All tests and test data from these locations are merged in the order indicated in the above list.
 
-The directories immediately follow above three paths use the same format and further sub-directories under each category are supported.
+Directories immediately following the above paths will use the same format, and sub-directories under each category are supported.
 
 ```tree
 <Path>