docs: fix various typos (#4903)

Author: Simek

STYLEGUIDE.md

@@ -137,4 +137,4 @@ When writing step-by-step instructions (e.g. how to install something), try to f
 
 ## Resources
 
-- [React JS’s contibuting guidelines](https://github.com/reactjs/reactjs.org/blob/main/CONTRIBUTING.md#guidelines-for-text), especially the [code examples guidelines](https://github.com/reactjs/reactjs.org/blob/master/CONTRIBUTING.md#guidelines-for-code-examples)
+- [React JS’s contributing guidelines](https://github.com/reactjs/reactjs.org/blob/main/CONTRIBUTING.md#guidelines-for-text), especially the [code examples guidelines](https://github.com/reactjs/reactjs.org/blob/master/CONTRIBUTING.md#guidelines-for-code-examples)

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

@@ -237,7 +237,7 @@ We now need to add some native code in order to start the React Native runtime a
 
 ### Requirements
 
-React Native intialization is now unbound to any specific part of an iOS app.
+React Native initialization is now unbound to any specific part of an iOS app.
 
 React Native can be initialized using a class called `RCTReactNativeFactory`, that takes care of handling the React Native lifecycle for you.
 

website/architecture/bundled-hermes.md

@@ -162,7 +162,7 @@ The prebuilt artifacts for Hermes do not contain debug symbols (dSYMs) by defaul
 
 ### I'm afraid this change is impacting me
 
-We'd like to stress that this is essentially an organizational change on _where_ Hermes is built and _how_ the code is syncronized between the two repositories. The change should be fully transparent to our users.
+We'd like to stress that this is essentially an organizational change on _where_ Hermes is built and _how_ the code is synchronized between the two repositories. The change should be fully transparent to our users.
 
 Historically, we used to cut a release of Hermes for a specific version of React Native (e.g. [`v0.11.0 for RN0.68.x`](https://github.com/facebook/hermes/releases/tag/v0.11.0)).
 

website/blog/2021-04-08-GAAD-March-Accessibility-Issue-Update.md

@@ -18,7 +18,7 @@ Thank you to all the community members who have participated. You are truly movi
 
 - [feat: set disabled accessibilityState when TouchableHighlight is disabled #31135](https://github.com/facebook/react-native/pull/31135) closed by [@natural_clar](https://twitter.com/natural_clar)
 
-- [[Android] Selected State does not annonce when TextInput Component selected #31144](https://github.com/facebook/react-native/pull/31144) closed by [fabriziobertoglio1987](https://fabriziobertoglio.xyz/)
+- [[Android] Selected State does not announce when TextInput Component selected #31144](https://github.com/facebook/react-native/pull/31144) closed by [fabriziobertoglio1987](https://fabriziobertoglio.xyz/)
 
 - [Added talkback support for TouchableNativeFeedback accessibility: disabled prop #31224](https://github.com/facebook/react-native/pull/31224) closed by [@kyamashiro73](https://twitter.com/kyamashiro73)
 

website/blog/2021-05-20-GAAD-One-Year-Later.md

@@ -88,7 +88,7 @@ We want to thank all the contributors mentioned below who have submitted and mer
 - [@natural_clar](https://twitter.com/natural_clar) closed 1 issue with:
   - [feat: set disabled accessibilityState when `TouchableHighlight` is disabled #31135](https://github.com/facebook/react-native/pull/31135)
 - [fabriziobertoglio1987](https://github.com/fabriziobertoglio1987) closed 2 issues with:
-  - [[Android] Selected State does not annonce when `TextInput` Component selected #31144](https://github.com/facebook/react-native/pull/31144)
+  - [[Android] Selected State does not announce when `TextInput` Component selected #31144](https://github.com/facebook/react-native/pull/31144)
   - [Accessibility Fix Image does not announce "disabled" #31252](https://github.com/facebook/react-native/pull/31252)
 - [@kyamashiro73](https://twitter.com/kyamashiro73) closed 1 issue with:
   - [Added talkback support for `TouchableNativeFeedback` accessibility: disabled prop #31224](https://github.com/facebook/react-native/pull/31224)

website/blog/2024-10-23-release-0.76-new-architecture.md

@@ -118,7 +118,7 @@ Like `boxShadow`, `filter` can take either a string, which mimics the CSS syntax
 
 ### Removed the dependency on the @react-native-community/cli
 
-As previosly shared in 0.75, our vision is for React Native to be [framework agnostic](https://github.com/react-native-community/discussions-and-proposals/blob/main/proposals/0759-react-native-frameworks.md). Therefore, we completed the work to remove @react-native-community/cli as a direct dependency of React Native.
+As previously shared in 0.75, our vision is for React Native to be [framework agnostic](https://github.com/react-native-community/discussions-and-proposals/blob/main/proposals/0759-react-native-frameworks.md). Therefore, we completed the work to remove @react-native-community/cli as a direct dependency of React Native.
 
 Decoupling React Native from the CLI allows us to move faster through releasing these projects independently and to better separate the responsibilities of both projects.
 

website/versioned_docs/version-0.78/_integration-with-existing-apps-ios.md

@@ -232,7 +232,7 @@ We now need to add some native code in order to start the React Native runtime a
 
 ### Requirements
 
-React Native intialization is now unbound to any specific part of an iOS app.
+React Native initialization is now unbound to any specific part of an iOS app.
 
 React Native can be initialized using a class called `RCTReactNativeFactory`, that takes care of handling the React Native lifecycle for you.
 

website/versioned_docs/version-0.79/_integration-with-existing-apps-ios.md

@@ -232,7 +232,7 @@ We now need to add some native code in order to start the React Native runtime a
 
 ### Requirements
 
-React Native intialization is now unbound to any specific part of an iOS app.
+React Native initialization is now unbound to any specific part of an iOS app.
 
 React Native can be initialized using a class called `RCTReactNativeFactory`, that takes care of handling the React Native lifecycle for you.
 

website/versioned_docs/version-0.79/the-new-architecture/fabric-component-native-commands.md

@@ -4,7 +4,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con
 
 In the [base guide](/docs/fabric-native-components-introduction) to write a new Native Component, you have explored how to create a new component, how to pass properties from the JS side to the native side, and how to emit events from native side to JS.
 
-Custom components can also call some of the functions implementated in the native code imperatively, to achieve some more advanced functionalities, such as programmatically reload a web page.
+Custom components can also call some of the functions implemented in the native code imperatively, to achieve some more advanced functionalities, such as programmatically reload a web page.
 
 In this guide you'll learn how to achieve this, by using a new concept: Native Commands.
 

website/versioned_docs/version-0.80/_integration-with-existing-apps-ios.md

@@ -232,7 +232,7 @@ We now need to add some native code in order to start the React Native runtime a
 
 ### Requirements
 
-React Native intialization is now unbound to any specific part of an iOS app.
+React Native initialization is now unbound to any specific part of an iOS app.
 
 React Native can be initialized using a class called `RCTReactNativeFactory`, that takes care of handling the React Native lifecycle for you.