Update validation-process-and-information.md

Author: jasonbayton

_src/android/android-enterprise-device-support/validation-process-and-information.md

@@ -134,7 +134,7 @@ If the implementation is perfectly fine and requires no work, understandably the
 
 ### Retesting
 
-Retesting is always encouraged. When a device is retested, the version of the OS it originally tested against will be replaced as well as any changes updated on the supported devices page. The major version and point-release (ie 7.1, 6.0.1) of the OS tested will always be presented with the test results to ensure readers cannot assume the results apply to the device as a whole and not the particular context under which the validation was completed.
+Retesting is always encouraged. When a device is retested, the version of the OS it originally tested against will be replaced as well as any changes updated on the supported devices page. The major version and point-release (ie 7.1, 6.0.1, 13 QPR4) of the OS tested will always be presented with the test results to ensure readers cannot assume the results apply to the device as a whole and not the particular context under which the validation was completed.
 
 ### OEM/reseller information
 
@@ -158,19 +158,19 @@ https://twitter.com/rmohr/status/927181646473912321
 
 ### Why test devices?
 
-Android Enterprise is becoming popular, however not all OEMs fully support and/or implement the Android Enterprise APIs to the same standard. The goal of this project is therefore to document as many devices as possible in order to provide a free resource for organisations looking for devices validated to be fully compatible with Android Enterprise EMM deployments.
+Android Enterprise is popular, however not all OEMs fully support and/or implement the Android Enterprise APIs to the same standard, even those on the AER list. The goal of this project is therefore to document as many devices as possible in order to provide a free resource for organisations looking for devices validated to be fully compatible with Android Enterprise EMM deployments.
 
 As an example:
 
-The Motorola [Moto Z](/android/android-enterprise-device-support/#motorola-moto-z) and [Moto Z Play](/android/android-enterprise-device-support/#motorola-moto-z-play) both run Android 7.0 (at the time of testing), look, feel and behave in the exact same way, however while the Moto Z supports the full range of provisioning options, the Moto Z Play doesn’t provision via NFC correctly.
+The Motorola Moto Z and Moto Z Play both ran Android 7.0 at the time of testing, looked, felt and behaved in the exact same way, however while the Moto Z supported the full range of provisioning options, the Moto Z Play didn't provision via NFC correctly.
 
 These types of experiences are beneficial for organisations looking to purchase devices, ensuring only those fully supported are taken into consideration (or at the very least, understanding where devices are known to fall short).
 
 ### From where are devices sourced?
 
 Devices listed to date have either been purchased privately or loaned to me by an OEM or reseller. How I obtain the devices has zero impact on the results, however those I purchase myself generally receive [far more in-depth public reporting](https://plus.google.com/+JasonBaytonX/posts/4aY2cvziZDB) than those loaned to me with a nominated contact I can report my findings to.
 
-Clearly I cannot afford to buy every device on the market for testing, so I’m hugely reliant on support from OEMS and resellers interested in having devices independently validated. To date **Sony**, **Nokia**, **Huawei**, **CAT**, **BQ** and others have been supportive of this project. I’m currently seeking to make contact with HTC, LG, Lenovo (Motorola), Asus, BlackBerry, and *any other GMS-certified OEMs* to grow the list. If you’re an **OEM** or **reseller** of Android devices, I’d accept any device, appliance or custom hardware running Android 6.0.1 or later to independently test. Devices can be returned within a week or so. Use my [contact](/contact/) page to get in touch or [email me directly](mailto:jason@bayton.org).
+Clearly I cannot afford to buy every device on the market for testing, so I’m hugely reliant on support from OEMS and resellers interested in having devices independently validated. To date **Sony**, **Nokia**, **Huawei**, **CAT**, **BQ**, **Lenovo** and others have been supportive of this project. I’m currently seeking to make contact with HTC, Asus, OnePlus, Nothing, and *any other GMS-certified OEMs in the consumer, dedicated, or rugged space* to grow the list. If you’re an **OEM** or **reseller** of Android devices, I’d accept any device, appliance or custom hardware running Android 10 or later to independently test. Devices can be returned within a week or so. Use my [contact](/contact/) page to get in touch or [email me directly](mailto:jason@bayton.org).
 
 If you’re an **organisation** evaluating devices for deployment and wish to have them externally tested, you are also by all means welcome to contact me to discuss this also.
 
@@ -182,8 +182,7 @@ Yes, this information could be sourced elsewhere, however it is:
 
 1. Naturally biased – all OEMs can say they support Android Enterprise, but not to what degree or if it’s 100% correctly implemented.
 2. Nowhere near as in-depth as my testing – each provisioning method, each deployment scenario, EMM compatibility, and more.
-3. Not publicly published alongside competing devices for ease of comparison.
-4. Not objectively tested by an independent 3rd party (which ties back into 1.).
+3. Not objectively tested by an independent 3rd party (which ties back into 1.).
 
 ## Contact