fix(docs): typos (#7965)

* fix: `resource` typo

* fix: `initialized` typo

* fix: `initialize` typo

* fix: `minimized` typo

* chore: trigger cla-action

Author: shubh73

docs/crashlytics/usage/index.md

@@ -120,7 +120,7 @@ export default function App() {
     try {
       if (users) {
         // An empty array is truthy, but not actually true.
-        // Therefore the array was never initialised.
+        // Therefore the array was never initialized.
         setUserCounts(userCounts.push(users.length));
       }
     } catch (error) {

docs/database/usage/index.md

@@ -341,7 +341,7 @@ For example:
 import database, { firebase } from '@react-native-firebase/database';
 
 // create a secondary app
-const secondaryApp = await firebase.initalizeApp(credentials, config);
+const secondaryApp = await firebase.initializeApp(credentials, config);
 
 // pass the secondary app instance to the database module
 const secondaryDatabase = database(secondaryApp);

docs/messaging/usage/index.md

@@ -115,7 +115,7 @@ scenarios, it is first important to establish the various states a device can be
 | State          | Description                                                                                                                                                                                               |
 | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | **Foreground** | When the application is open and in view.                                                                                                                                                                 |
-| **Background** | When the application is open, however in the background (minimised). This typically occurs when the user has pressed the "home" button on the device or has switched to another app via the app switcher. |
+| **Background** | When the application is open, however in the background (minimized). This typically occurs when the user has pressed the "home" button on the device or has switched to another app via the app switcher. |
 | **Quit**       | When the device is locked or application is not active or running. The user can quit an app by "swiping it away" via the app switcher UI on the device.                                                   |
 
 The user must have opened the app before messages can be received. If the user force quits the app from the device settings, it must be re-opened again before receiving messages.

docs/migrating-to-v6.md

@@ -450,7 +450,7 @@ How to migrate: If you use device-local notification APIs and user-visible notif
 - Module namespace has been renamed to `.remoteConfig()` from `.config()`.
 - All Remote Config values can now be accessed synchronously in JS, see `getValue(key: string): ConfigValue` & `getAll(): ConfigValues` below.
   - These replace all the original async methods: `getValue`, `getValues`, `getKeysByPrefix`.
-- `setDefaultsFromResource` now returns a Promise that resolves when completed, this will reject with code `config/resouce_not_found` if the file could not be found.
+- `setDefaultsFromResource` now returns a Promise that resolves when completed, this will reject with code `config/resource_not_found` if the file could not be found.
 - `setDefaultsFromResource` now expects a resource file name for Android to match iOS, formerly this required a resource id (something you would not have in RN as this was generated at build time by Android).
   - An example for both platforms can be found in the tests.
 - `enableDeveloperMode` has been removed, you can now use `setConfigSettings({ isDeveloperModeEnabled: boolean })` instead.

docs/releases/v6.0.0.md

@@ -268,7 +268,7 @@ The Remote Config API has had a significant API change as originally highlighted
 - [BREAKING] Module namespace has been renamed to `.remoteConfig()`, replace all usages of `firebase.config` with the new name.
 - [BREAKING] All Remote Config values can now be accessed synchronously in JS, see `getValue(key: string): ConfigValue` & `getAll(): ConfigValues` below
   - [BREAKING] These replace all the original async methods: `getValue`, `getValues`, `getKeysByPrefix`
-- [BREAKING] `setDefaultsFromResource` now returns a Promise that resolves when completed, this will reject with code `config/resouce_not_found` if the file could not be found
+- [BREAKING] `setDefaultsFromResource` now returns a Promise that resolves when completed, this will reject with code `config/resource_not_found` if the file could not be found
 - [BREAKING] `setDefaultsFromResource` now expects a resource file name for Android to match iOS, formerly this required a resource id (something you would not have in RN as this was generated at build time by Android)
   - And example for both platforms can be found in the tests.
 - [BREAKING] `enableDeveloperMode` has been removed, you can now use `setConfigSettings({ isDeveloperModeEnabled: boolean })` instead