docs: spell-check some docs

website/docs/FAQ.md

@@ -3,42 +3,40 @@ id: faq
 title: FAQ
 ---
 
-<details>
-  <summary>Can I test native features of React Native apps?</summary>
+#### Can I test the native features of React Native apps?
 
-<p>Short answer: no.</p>
+Short answer: no.
 
-React Native Testing Library does not provide a full React Native runtime since that would require running on physical device
+React Native Testing Library does not provide an entire React Native runtime since that would require running on a physical device
 or iOS simulator/Android emulator to provision the underlying OS and platform APIs.
 
-Instead of using React Native renderer, it simulates only the JavaScript part of its runtime by
+Instead of using React Native renderer, it simulates only the JavaScript part of its runtime
 using [React Test Renderer](https://reactjs.org/docs/test-renderer.html) while providing queries
-and `fireEvent` APIs that mimick certain behaviors from the real runtime.
+and event APIs (`userEvent`, `fireEvent`) that mimicking certain behaviors from the actual runtime.
 
 You can learn more about our testing environment [here](./TestingEnvironment.md).
 
-This approach has certain benefits and shortfalls. On the positive side:
+This approach has specific benefits and shortfalls. On the positive side:
 
 - it allows testing most of the logic of regular React Native apps
-- it allows running test on any OS supported by Jest, or other test runner, e.g. on CI
+- it allows running tests on any OS supported by Jest or other test runners, e.g., on CI
 - it uses much less resources than full runtime simulation
 - you can use Jest fake timers
 
-The the negative side:
+On the negative side:
 
 - you cannot test native features
-- certain JavaScript features might not be perfectly simulated, but we are working on it
+- it might not perfectly simulate certain JavaScript features, but we are working on it
 
-For instance, [react-native's ScrollView](https://reactnative.dev/docs/scrollview) has several props that depend on native calls. While you can trigger `onScroll` call with `fireEvent.scroll`, `onMomentumScrollBegin` is called from the native side and will therefore not be called.
+The [User Event interactions](user-event) solve some of the simulation issues, as they offer more realistic event handling than the basic [Fire Event API](api#fireevent-api).
 
-</details>
-
-<details>
-  <summary>Should I use/migrate to `screen` queries?</summary>
+### Should I use/migrate to `screen` queries?
 
 There is no need to migrate existing test code to use `screen`-bases queries. You can still use
-queries and other functions returned by `render`. In fact `screen` hold just that value, the latest `render` result.
+queries and other functions returned by `render`. The `screen` object captures the latest `render` result.
+
+For new code, you are encouraged to use `screen` as there are some good reasons for that, which are described in [this article](https://kentcdodds.com/blog/common-mistakes-with-react-testing-library#not-using-screen) by Kent C. Dodds.
 
-For newer code you can either use `screen` or `render` result destructuring. However, there are some good reasons to use `screen`, which are described in [this article](https://kentcdodds.com/blog/common-mistakes-with-react-testing-library#not-using-screen) by Kent C. Dodds.
+### Should I use/migrate to User Event interactions?
 
-</details>
+We encourage you to migrate existing tests to use the [User Event interactions](user-event), which offer more realistic event handling than the basic [Fire Event API](api#fireevent-api). Hence, it will provide more confidence in the quality of your code.

website/docs/GettingStarted.md

@@ -5,17 +5,17 @@ title: Getting Started
 
 ## The problem
 
-You want to write maintainable tests for your React Native components. As a part of this goal, you want your tests to avoid including implementation details of your components and rather focus on making your tests give you the confidence for which they are intended. As part of this, you want your testbase to be maintainable in the long run so refactors of your components (changes to implementation but not functionality) don't break your tests and slow you and your team down.
+You want to write maintainable tests for your React Native components. As a part of this goal, you want your tests to avoid including implementation details of your components and focus on making your tests give you the confidence they are intended. As part of this, you want your tests to be maintainable in the long run so refactors of your components (changes to implementation but not functionality) don't break your tests and slow you and your team down.
 
 ## This solution
 
-The React Native Testing Library (RNTL) is a lightweight solution for testing React Native components. It provides light utility functions on top of `react-test-renderer`, in a way that encourages better testing practices. Its primary guiding principle is:
+The React Native Testing Library (RNTL) is a lightweight solution for testing React Native components. It provides light utility functions on top of React Test Renderer, in a way that encourages better testing practices. Its primary guiding principle is:
 
-> The more your tests resemble the way your software is used, the more confidence they can give you.
+> The more your tests resemble how your software is used, the more confidence they can give you.
 
-This project is inspired by [React Testing Library](https://github.com/testing-library/react-testing-library). Tested to work with Jest, but it should work with other test runners as well.
+This project is inspired by [React Testing Library](https://github.com/testing-library/react-testing-library). It is tested to work with Jest, but it should work with other test runners as well.
 
-You can find the source of `QuestionsBoard` component and this example [here](https://github.com/callstack/react-native-testing-library/blob/main/src/__tests__/questionsBoard.test.tsx).
+You can find the source of the `QuestionsBoard` component and this example [here](https://github.com/callstack/react-native-testing-library/blob/main/src/__tests__/questionsBoard.test.tsx).
 
 ## Installation
 
@@ -33,15 +33,15 @@ yarn add --dev @testing-library/react-native
 npm install --save-dev @testing-library/react-native
 ```
 
-This library has a `peerDependencies` listing for `react-test-renderer`. Make sure that your `react-test-renderer` version matches exactly your `react` version.
+This library has a peer dependency for `react-test-renderer` package. Make sure that your `react-test-renderer` version matches exactly your `react` version.
 
 :::info
-In order to properly use helpers for async tests (`findBy` queries and `waitFor`) you need at least React >=16.9.0 (featuring async `act`) or React Native >=0.61 (which comes with React >=16.9.0).
+To properly use helpers for async tests (`findBy` queries and `waitFor`), you need at least React >=16.9.0 (featuring async `act`) or React Native >=0.61 (which comes with React >=16.9.0).
 :::
 
 ### Additional Jest matchers
 
-In order to use additional React Native-specific Jest matchers add the following line to your `jest-setup.ts` file (configured using [`setupFilesAfterEnv`](https://jestjs.io/docs/configuration#setupfilesafterenv-array)):
+To use additional React Native-specific Jest matchers, add the following line to your `jest-setup.ts` file (configured using [`setupFilesAfterEnv`](https://jestjs.io/docs/configuration#setupfilesafterenv-array)):
 
 ```ts
 import '@testing-library/react-native/extend-expect';
@@ -80,4 +80,4 @@ test('form submits two answers', () => {
 });
 ```
 
-You can find the source of `QuestionsBoard` component and this example [here](https://github.com/callstack/react-native-testing-library/blob/main/src/__tests__/questionsBoard.test.tsx).
+You can find the source of the `QuestionsBoard` component and this example [here](https://github.com/callstack/react-native-testing-library/blob/main/src/__tests__/questionsBoard.test.tsx).