fix typos, backport recent fixes to versioned docs (facebook#4188)

Author: Simek

docs/_integration-with-existing-apps-java.md

@@ -124,7 +124,7 @@ dependencies {
 }
 ```
 
-Those depedencies are available on `mavenCentral()` so make sure you have it defined in your `repositories{}` block.
+Those dependencies are available on `mavenCentral()` so make sure you have it defined in your `repositories{}` block.
 
 :::info
 We intentionally don't specify the version for those `implementation` dependencies as the React Native Gradle Plugin will take care of it. If you don't use the React Native Gradle Plugin, you'll have to specify version manually.

docs/_integration-with-existing-apps-kotlin.md

@@ -124,7 +124,7 @@ dependencies {
 }
 ```
 
-Those depedencies are available on `mavenCentral()` so make sure you have it defined in your `repositories{}` block.
+Those dependencies are available on `mavenCentral()` so make sure you have it defined in your `repositories{}` block.
 
 :::info
 We intentionally don't specify the version for those `implementation` dependencies as the React Native Gradle Plugin will take care of it. If you don't use the React Native Gradle Plugin, you'll have to specify version manually.

docs/flatlist.md

@@ -22,7 +22,7 @@ If you need section support, use [`<SectionList>`](sectionlist.md).
 
 ## Example
 
-<Tabs groupId="language" queryString defaultValue={constants.dewfaultSnackLanguage} values={constants.snackLanguages}>
+<Tabs groupId="language" queryString defaultValue={constants.defaultSnackLanguage} values={constants.snackLanguages}>
 <TabItem value="javascript">
 
 ```SnackPlayer name=flatlist-simple&ext=js
@@ -166,7 +166,7 @@ More complex, selectable example below.
 - By passing `extraData={selectedId}` to `FlatList` we make sure `FlatList` itself will re-render when the state changes. Without setting this prop, `FlatList` would not know it needs to re-render any items because it is a `PureComponent` and the prop comparison will not show any changes.
 - `keyExtractor` tells the list to use the `id`s for the react keys instead of the default `key` property.
 
-<Tabs groupId="language" queryString defaultValue={constants.dewfaultSnackLanguage} values={constants.snackLanguages}>
+<Tabs groupId="language" queryString defaultValue={constants.defaultSnackLanguage} values={constants.snackLanguages}>
 <TabItem value="javascript">
 
 ```SnackPlayer name=flatlist-selectable&ext=js

docs/flexbox.md

@@ -2080,7 +2080,7 @@ export default App;
 
 - [`gap`](layout-props#gap) sets the size of the gap (gutter) between rows and columns. It is a shorthand for `rowGap` and `columnGap`.
 
-You can use `flexWrap` and `alignContent` alongwith `gap` to add consistent spacing between items.
+You can use `flexWrap` and `alignContent` along with `gap` to add consistent spacing between items.
 
 <Tabs groupId="language" queryString defaultValue={constants.defaultSnackLanguage} values={constants.snackLanguages}>
 <TabItem value="javascript">

docs/native-modules-ios.md

@@ -288,7 +288,7 @@ For iOS, you can also write native module methods with any argument type that is
 
 ### Exporting Constants
 
-A native module can export constants by overriding the native method `constantsToExport()`. Below `constantsToExport()` is overriden, and returns a Dictionary that contains a default event name property you can access in JavaScript like so:
+A native module can export constants by overriding the native method `constantsToExport()`. Below `constantsToExport()` is overridden, and returns a Dictionary that contains a default event name property you can access in JavaScript like so:
 
 ```objectivec
 - (NSDictionary *)constantsToExport

docs/running-on-simulator-ios.md

@@ -53,7 +53,7 @@ The device names correspond to the list of devices available in Xcode. You can c
 
 ### Specifying a version of device
 
-If you have multiple iOS versions installed, you also need to specify it's appropiate version. E.g. To run your app on an iPhone 14 Pro (16.0) run the following command:
+If you have multiple iOS versions installed, you also need to specify its appropriate version. E.g. To run your app on an iPhone 14 Pro (16.0) run the following command:
 
 <Tabs groupId="package-manager" queryString defaultValue={constants.defaultPackageManager} values={constants.packageManagers}>
 <TabItem value="npm">

docs/scrollview.md

@@ -413,7 +413,7 @@ Enables nested scrolling for Android API level 21+.
 
 Called when scrollable content view of the ScrollView changes.
 
-The handler function will recieve two parameters: the content width and content height `(contentWidth, contentHeight)`.
+The handler function will receive two parameters: the content width and content height `(contentWidth, contentHeight)`.
 
 It's implemented using onLayout handler attached to the content container which this ScrollView renders.
 

website/versioned_docs/version-0.70/linking.md

@@ -303,7 +303,7 @@ Determine whether or not an installed app can handle a given URL.
 
 The method returns a `Promise` object. When it is determined whether or not the given URL can be handled, the promise is resolved and the first parameter is whether or not it can be opened.
 
-The `Promise` will reject on Android if it was impossible to check if the URL can be opened or when targetting Android 11 (SDK 30) if you didn't specify the relevant intent queries in `AndroidManifest.xml`. Similarly on iOS, the promise will reject if you didn't add the specific scheme in the `LSApplicationQueriesSchemes` key inside `Info.plist` (see bellow).
+The `Promise` will reject on Android if it was impossible to check if the URL can be opened or when targeting Android 11 (SDK 30) if you didn't specify the relevant intent queries in `AndroidManifest.xml`. Similarly on iOS, the promise will reject if you didn't add the specific scheme in the `LSApplicationQueriesSchemes` key inside `Info.plist` (see bellow).
 
 **Parameters:**
 

website/versioned_docs/version-0.70/native-modules-ios.md

@@ -274,7 +274,7 @@ For iOS, you can also write native module methods with any argument type that is
 
 ### Exporting Constants
 
-A native module can export constants by overriding the native method `constantsToExport()`. Below `constantsToExport()` is overriden, and returns a Dictionary that contains a default event name property you can access in JavaScript like so:
+A native module can export constants by overriding the native method `constantsToExport()`. Below `constantsToExport()` is overridden, and returns a Dictionary that contains a default event name property you can access in JavaScript like so:
 
 ```objectivec
 - (NSDictionary *)constantsToExport

website/versioned_docs/version-0.70/running-on-simulator-ios.md

@@ -15,7 +15,7 @@ The device names correspond to the list of devices available in Xcode. You can c
 
 ### Specifying a version of device
 
-If you have multiple iOS versions installed, you also need to specify it's appropiate version. E.g. run `npx react-native run-ios --simulator='iPhone 13 Pro (15.5)'` in order to specify the iOS version.
+If you have multiple iOS versions installed, you also need to specify its appropriate version. E.g. run `npx react-native run-ios --simulator='iPhone 13 Pro (15.5)'` in order to specify the iOS version.
 
 ## Specifying an UDID