docs: fix lint errors

Author: noomorph

.retext-spell.dic

@@ -1,3 +1,4 @@
+AAPT/M
 AAR/M
 ANR/M
 AOSP/M
@@ -64,6 +65,7 @@ beforeAll
 beforeEach
 biometric
 blob/M
+blogpost/M
 breakpoint/M
 bundler
 cancelled
@@ -97,6 +99,7 @@ lockfile/M
 macOS
 matcher/M
 minification/M
+minSdkVersion
 monorepo
 multistep
 natively
@@ -145,6 +148,7 @@ unminified
 unobfuscated
 unregister/M
 util/M
+v12.x
 webhook/M
 websocket/M
 xcodebuild

docs/Guide.Mocking.md

@@ -64,7 +64,7 @@ Let's start with the quicker way.
 
    This command is already enough to start your application in an altered mode, and you can start running your tests. Now, if some module imports `./src/config`, you tell _Metro bundler_ to prefer `./src/config.mock.js` over the plain `./src/config.js`, which means the consumer gets the mocked implementation.
 
-> CAVEAT: whichever file extension you might take for the mock files – make sure you don't accidentally "pick up" unforeseen file overrides from `node_modules/**/*.your-extension.js`!
+> CAVEAT: whichever file extension you might take for the mock files – make sure you don’t accidentally "pick up" unforeseen file overrides from `node_modules/**/*.your-extension.js`!
 > _Metro bundler_ does not limit itself to your project files only – applying those `--sourceExts` also affects the resolution of the `node_modules` content!
 
 ### Configuring Metro bundler

docs/Introduction.Android.md

@@ -301,7 +301,7 @@ Setting Test Butler up for working with Detox is a bit different than explained
 
 The library part can be easily achieved as explained there (i.e. by using Gradle’s `androidTestImplementation`). Same goes for initialization. As for the APK, the suggested usage of Gradle’s `androidTestUtil` is scarce when running with Detox (i.e. non-native instrumentation tests). Here’s what to do instead.
 
-> _For a complete and thorough coverage of the Test Bulter integration with Detox, consider going over our [blogpost on CI execution](https://medium.com/wix-engineering/how-to-execute-android-ui-tests-on-ci-and-stay-alive-eb9089d88c1f) on medium_.
+> _For a complete and thorough coverage of the Test Butler integration with Detox, consider going over our [blogpost on CI execution](https://medium.com/wix-engineering/how-to-execute-android-ui-tests-on-ci-and-stay-alive-eb9089d88c1f) on medium_.
 
 ##### Solution 1: Prebaked Images
 

docs/Introduction.AndroidDevEnv.md

@@ -101,7 +101,7 @@ While it’s possible to do this using Android Studio, we’ll focus on the comm
 
    > - With `;android-28;`, we assumed SDK 28 here, but other APIs are supported just the same.
    > - The `;default;` part replaces `;google_apis;`, which is the default, and is what matters here.
-   > - If you are running on a M1 you must install a arm64 architecture i.e. `system-images;android-28;default;arm64-v8a`
+   > - If you are running on a M1 you must install an arm64 architecture i.e. `system-images;android-28;default;arm64-v8a`
 
 1. Create an emulator (i.e. AVD - Android Virtual Device):
 

website/versioned_docs/version-19.x/Introduction.Android.md

@@ -301,7 +301,7 @@ Setting Test Butler up for working with Detox is a bit different than explained
 
 The library part can be easily achieved as explained there (i.e. by using Gradle’s `androidTestImplementation`). Same goes for initialization. As for the APK, the suggested usage of Gradle’s `androidTestUtil` is scarce when running with Detox (i.e. non-native instrumentation tests). Here’s what to do instead.
 
-> _For a complete and thorough coverage of the Test Bulter integration with Detox, consider going over our [blogpost on CI execution](https://medium.com/wix-engineering/how-to-execute-android-ui-tests-on-ci-and-stay-alive-eb9089d88c1f) on medium_.
+> _For a complete and thorough coverage of the Test Butler integration with Detox, consider going over our [blogpost on CI execution](https://medium.com/wix-engineering/how-to-execute-android-ui-tests-on-ci-and-stay-alive-eb9089d88c1f) on medium_.
 
 ##### Solution 1: Prebaked Images
 

website/versioned_docs/version-19.x/Introduction.AndroidDevEnv.md

@@ -101,7 +101,7 @@ While it’s possible to do this using Android Studio, we’ll focus on the comm
 
    > - With `;android-28;`, we assumed SDK 28 here, but other APIs are supported just the same.
    > - The `;default;` part replaces `;google_apis;`, which is the default, and is what matters here.
-   > - If you are running on a M1 you must install a arm64 architecture i.e. `system-images;android-28;default;arm64-v8a`
+   > - If you are running on a M1 you must install an arm64 architecture i.e. `system-images;android-28;default;arm64-v8a`
 
 1. Create an emulator (i.e. AVD - Android Virtual Device):