typos

Author: jasonbayton

_src/android/android-enterprise-device-support/google-pixel-3a-validation-report.md

@@ -124,10 +124,10 @@ There are numerous issues with the MobileIron kiosk, these are not limited to th
 - No access to settings other than those explicitly permitted
 - Kiosk auto-launches
 
-Despite the relevant configurations in place, it is effortless to escape the MobileIron kiosk if any access to settings has been granted. For example should WiFi settings be available:
+Despite the relevant configurations in place, it is effortless to escape the MobileIron kiosk if any access to settings has been granted. For example should Wi-Fi settings be available:
 
 - Tap kiosk settings
-- Tap WiFi
+- Tap Wi-Fi
 - In the systems settings screen, tap the back arrow or hamburger menu
 - Full settings access is granted
 

_src/android/android-enterprise-device-support/honor-play-android-enterprise-validation-report.md

@@ -56,7 +56,7 @@ The process otherwise runs without issue, and behaves as expected.
 
 Zero-touch provisioning **is possible**, however the manufacturer ID must be Honor’s parent company, Huawei, when importing devices into the zero-touch portal.
 
-The only recommendation would be to reorder the setup wizard somewhat, it should not be necessary to navigate through a number of steps before even being prompted for WiFi (which does not auto-continue once connected, requiring one more manual tap).
+The only recommendation would be to reorder the setup wizard somewhat, it should not be necessary to navigate through a number of steps before even being prompted for Wi-Fi (which does not auto-continue once connected, requiring one more manual tap).
 
 ![](https://cdn.bayton.org/uploads/2019/03/Screenshot_20190326_233941_com.huawei.hwstartupguide.jpg)
 

_src/android/android-enterprise-device-support/moto-g7-power-android-enterprise-validation-report.md

@@ -123,10 +123,10 @@ There are numerous issues with the MobileIron kiosk, these are not limited to th
 - No access to settings other than those explicitly permitted
 - Kiosk auto-launches
 
-Despite the relevant configurations in place, it is effortless to escape the MobileIron kiosk if any access to settings has been granted. For example should WiFi settings be available:
+Despite the relevant configurations in place, it is effortless to escape the MobileIron kiosk if any access to settings has been granted. For example should Wi-Fi settings be available:
 
 - Tap kiosk settings
-- Tap WiFi
+- Tap Wi-Fi
 - In the systems settings screen, tap the back arrow or hamburger menu
 - Full settings access is granted
 

_src/android/android-enterprise-device-support/oneplus-6t-validation-report.md

@@ -90,7 +90,7 @@ A. Disabling addition of accounts on work profile prevents it on fully managed a
 ### 3.4. COSU (Dedicated)  
 
 
-A. Full access to device settings, bypasses restrictions when entering settings like wifi, bluetooth, location, through the kiosk menu (MI Core)
+A. Full access to device settings, bypasses restrictions when entering settings like Wi-Fi, bluetooth, location, through the kiosk menu (MI Core)
 
 ## 4. Recommendation
 

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

@@ -74,7 +74,7 @@ Below is a list of checks undertaken for each provisioning process. For fully ma
 
 #### Zero-touch
 
-- Does not display the first run wizard after connecting to WiFi and instead after successful provisioning, goes directly to the home screen. 
+- Does not display the first run wizard after connecting to Wi-Fi and instead after successful provisioning, goes directly to the home screen. 
   - This includes “setup complete”, “OEM account” or permissions screens not directly related to the DPC being installed.
 - Correctly passes through DPC extras (like EMM server name, user ID, etc)
 - Performs a factory reset if not enrolled into EMM within one hour of provisioning, or if provisioning was bypassed.

_src/android/android-enterprise-faq/aer-device-issues.md

@@ -21,7 +21,7 @@ The first point of contact for any device based issue would be the EMM vendor. W
 
 Before contacting the EMM, the organisation should ensure the issue can be replicated on more than one device. If so, attempt to collect logs from the EMM, the device (a bug report, though be aware this will collect personal account information also) and steps to replicate it along with all of the normal details – make, model, Android version, build number, etc. A video is always appreciated though do add the steps on paper also.
 
-If the EMM can replicate it but cannot resolve it, they will have OEM contacts to reach out to to progress it. If necessary, Google will be involved once all other avenues are exhausted, or it’s determined to be a platform issue.
+If the EMM can replicate it but cannot resolve it, they will have OEM contacts to reach out to progress it. If necessary, Google will be involved once all other avenues are exhausted, or it’s determined to be a platform issue.
 
 I do a fair amount of device testing, so if you do come across something and your EMM is not providing the support needed, feel free to [reach out](/contact) and I’ll be happy to help.
 

_src/android/android-enterprise-faq/bind-ae-with-multiple-emms.md

@@ -18,7 +18,7 @@ eleventyNavigation:
 
 Historically this has not been possible. An Android Enterprise ID (organisation ID) is associated with only one EMM at a time, and a Google account can only manage one bind at a time; under all normal circumstances attempting to bind with the same Google account on another EMM will return an error stating an Enterprise already exists.
 
-From mid-2024 howeverr, with the roll-out of Google's Better Together Enterprise project designed to bring the enterprise arms of Google Cloud, Google Chrome/ChromeOS, and Android under one domain-managed account, this is no longer a limitation. 
+From mid-2024 however, with the roll-out of Google's new customer signup process designed to bring the enterprise arms of Google Cloud, Google Chrome/ChromeOS, and Android under one domain-managed account, this is no longer a limitation. 
 
 With a new, enterprise domain-led bind approach, all organisations binding with their EMMs will be able to create an organisation account associated with a zero-cost managed Google Enterprise domain (think Google Workspace, or perhaps more apt, a Google Cloud Identity tenant). With this approach, once the domain is verified as owned by the organisation, multiple EMMs (or multiple accounts under one EMM) can create as many organisation IDs as desired, and all will be managed under one Google Enterprise console.
 
@@ -30,4 +30,4 @@ _Attempting to bind with the same Google account on another EMM will return an e
 
 The only exception to the above is in high availability and/or disaster recovery scenarios where an instance of an EMM may be replicated, but no two EMMs should be generating managed Google Play accounts from the same Google account simultaneously.
 
-Google are expected to support migrations to BTE for existing organisations in the future.
+Google are expected to support migrations to Google Workspace domains for existing organisations in the future.

_src/android/android-enterprise-faq/configure-chrome-bookmarks.md

@@ -50,6 +50,6 @@ Be aware on managed Android devices, bookmarks [can't be placed on the home scre
 
 Other things to consider - 
 - The order you input the subfolders and URLs reflects directly in Chrome
-- If you input a child folder (eg: `"children"`), ensure you list the name (eg: `"name":"Internal URLs"`)
+- If you input a child folder (e.g.: `"children"`), ensure you list the name (e.g.: `"name":"Internal URLs"`)
 - All normal json rules apply. You can use a json validator to be sure it's valid before committing it
 - If Chrome doesn't show the bookmarks, though other configs (eg homepage) change, the syntax is invalid

_src/android/android-enterprise-faq/does-android-support-kerberos.md

@@ -19,7 +19,7 @@ No.
 
 I’d recommend taking a look at [Hypergate](https://hypergate.com).
 
-There is however a project which was initiated (but not wholly supported) by Google to bring Kerberos support to Android through an application. Take a look at the respective [Github repo](https://github.com/google/android-kerberos-authenticator) to learn more.
+There is however a project which was initiated (but not wholly supported) by Google to bring Kerberos support to Android through an application. Take a look at the respective [GitHub repo](https://github.com/google/android-kerberos-authenticator) to learn more.
 
 Related: [Setup Kerberos Authentication on MobileIron Core for Android Enterprise](/docs/enterprise-mobility/mobileiron/setup-kerberos-authentication-on-mobileiron-core-for-android-enterprise/)
 

_src/android/android-enterprise-faq/does-intune-support-cope.md

@@ -17,5 +17,5 @@ eleventyNavigation:
 --- 
 Yes.
 
-As of 2020, Intune supports work profiles on fully managed devices from Android 8.0. This is because Google’s [Android Management API introduced support](/2020/07/googles-android-management-api-will-soon-support-cope/) for the deployment scenario (albeit silently, intentionally avoiding stating as such in it’s wider Android 11 COPE announcement).
+As of 2020, Intune supports work profiles on fully managed devices from Android 8.0. This is because Google’s [Android Management API introduced support](/2020/07/googles-android-management-api-will-soon-support-cope/) for the deployment scenario (albeit silently, intentionally avoiding stating as such in its wider Android 11 COPE announcement).