tweaks

Author: mdjastrzebski

website/docs/13.x/docs/api/jest-matchers.mdx

@@ -1,6 +1,6 @@
 # Jest matchers
 
-This guide describes built-in Jest matchers. We recommend using these matchers as they provide readable tests, accessibility support, and a better developer experience.
+This guide describes built-in Jest matchers. These matchers provide readable assertions with accessibility support.
 
 ## Setup
 
@@ -18,7 +18,7 @@ If you are already using legacy Jest Native matchers we have a [migration guide]
 expect(element).toBeOnTheScreen();
 ```
 
-This allows you to assert whether an element is attached to the element tree or not. If you hold a reference to an element and it gets unmounted during the test it will no longer pass this assertion.
+Checks if an element is attached to the element tree. If you hold a reference to an element and it gets unmounted during the test, it will no longer pass this assertion.
 
 ## Element Content
 
@@ -34,7 +34,7 @@ expect(element).toHaveTextContent(
 )
 ```
 
-This allows you to assert whether the given element has the given text content or not. It accepts either `string` or `RegExp` matchers, as well as [text match options](/docs/api/queries#text-match-options) of `exact` and `normalizer`.
+Checks if the element has the specified text content. Accepts `string` or `RegExp` matchers, as well as [text match options](/docs/api/queries#text-match-options) of `exact` and `normalizer`.
 
 ### `toContainElement()`
 
@@ -44,15 +44,15 @@ expect(container).toContainElement(
 )
 ```
 
-This allows you to assert whether the given container element does contain another host element.
+Checks if the container element contains another host element.
 
 ### `toBeEmptyElement()`
 
 ```ts
 expect(element).toBeEmptyElement();
 ```
 
-This allows you to assert whether the given element does not have any host child elements or text content.
+Checks if the element has no host child elements or text content.
 
 ## Checking element state
 
@@ -68,7 +68,7 @@ expect(element).toHaveDisplayValue(
 )
 ```
 
-This allows you to assert whether the given `TextInput` element has a specified display value. It accepts either `string` or `RegExp` matchers, as well as [text match options](/docs/api/queries#text-match-options) of `exact` and `normalizer`.
+Checks if the `TextInput` element has the specified display value. Accepts `string` or `RegExp` matchers, as well as [text match options](/docs/api/queries#text-match-options) of `exact` and `normalizer`.
 
 ### `toHaveAccessibilityValue()`
 
@@ -83,7 +83,7 @@ expect(element).toHaveAccessibilityValue(
 )
 ```
 
-This allows you to assert whether the given element has a specified accessible value.
+Checks if the element has a specified accessible value.
 
 This matcher will assert accessibility value based on `aria-valuemin`, `aria-valuemax`, `aria-valuenow`, `aria-valuetext` and `accessibilityValue` props. Only defined value entries will be used in the assertion, the element might have additional accessibility value entries and still be matched.
 
@@ -96,7 +96,7 @@ expect(element).toBeEnabled();
 expect(element).toBeDisabled();
 ```
 
-These allow you to assert whether the given element is enabled or disabled from the user's perspective. It relies on the accessibility disabled state as set by `aria-disabled` or `accessibilityState.disabled` props. It will consider a given element disabled when it or any of its ancestors is disabled.
+Checks if the element is enabled or disabled from the user's perspective. These rely on the accessibility disabled state set by `aria-disabled` or `accessibilityState.disabled` props. An element is considered disabled when it or any of its ancestors is disabled.
 
 :::note
 These matchers are the negation of each other, and both are provided to avoid double negations in your assertions.
@@ -108,7 +108,7 @@ These matchers are the negation of each other, and both are provided to avoid do
 expect(element).toBeSelected();
 ```
 
-This allows you to assert whether the given element is selected from the user's perspective. It relies on the accessibility selected state as set by `aria-selected` or `accessibilityState.selected` props.
+Checks if the element is selected from the user's perspective. Relies on the accessibility selected state set by `aria-selected` or `accessibilityState.selected` props.
 
 ### `toBeChecked()` / `toBePartiallyChecked()` {#tobechecked}
 
@@ -117,7 +117,7 @@ expect(element).toBeChecked();
 expect(element).toBePartiallyChecked();
 ```
 
-These allow you to assert whether the given element is checked or partially checked from the user's perspective. It relies on the accessibility checked state as set by `aria-checked` or `accessibilityState.checked` props.
+Checks if the element is checked or partially checked from the user's perspective. These rely on the accessibility checked state set by `aria-checked` or `accessibilityState.checked` props.
 
 :::note
 
@@ -133,7 +133,7 @@ expect(element).toBeExpanded();
 expect(element).toBeCollapsed();
 ```
 
-These allow you to assert whether the given element is expanded or collapsed from the user's perspective. They rely on the accessibility expanded state as set by `aria-expanded` or `accessibilityState.expanded` props.
+Checks if the element is expanded or collapsed from the user's perspective. These rely on the accessibility expanded state set by `aria-expanded` or `accessibilityState.expanded` props.
 
 :::note
 These matchers are the negation of each other for expandable elements (elements with explicit `aria-expanded` or `accessibilityState.expanded` props). However, both won't pass for non-expandable elements (ones without explicit `aria-expanded` or `accessibilityState.expanded` props).
@@ -145,7 +145,7 @@ These matchers are the negation of each other for expandable elements (elements
 expect(element).toBeBusy();
 ```
 
-This allows you to assert whether the given element is busy from the user's perspective. It relies on the accessibility busy state as set by `aria-busy` or `accessibilityState.busy` props.
+Checks if the element is busy from the user's perspective. Relies on the accessibility busy state set by `aria-busy` or `accessibilityState.busy` props.
 
 ## Checking element style
 
@@ -155,7 +155,7 @@ This allows you to assert whether the given element is busy from the user's pers
 expect(element).toBeVisible();
 ```
 
-This allows you to assert whether the given element is visible from the user's perspective.
+Checks if the element is visible from the user's perspective.
 
 The element is considered invisible when itself or any of its ancestors has `display: none` or `opacity: 0` styles, as well as when it's hidden from accessibility.
 
@@ -167,7 +167,7 @@ expect(element).toHaveStyle(
 )
 ```
 
-This allows you to assert whether the given element has given styles.
+Checks if the element has the specified styles.
 
 ## Other matchers
 
@@ -183,7 +183,7 @@ expect(element).toHaveAccessibleName(
 )
 ```
 
-This allows you to assert whether the given element has a specified accessible name. It accepts either `string` or `RegExp` matchers, as well as [text match options](/docs/api/queries#text-match-options) of `exact` and `normalizer`.
+Checks if the element has the specified accessible name. Accepts `string` or `RegExp` matchers, as well as [text match options](/docs/api/queries#text-match-options) of `exact` and `normalizer`.
 
 The accessible name will be computed based on `aria-labelledby`, `accessibilityLabelledBy`, `aria-label`, and `accessibilityLabel` props, in the absence of these props, the element text content will be used.
 
@@ -198,7 +198,7 @@ expect(element).toHaveProp(
 )
 ```
 
-This allows you to assert whether the given element has a given prop. When the `value` parameter is `undefined` it will only check for existence of the prop, and when `value` is defined it will check if the actual value matches passed value.
+Checks if the element has the specified prop. When `value` is `undefined`, it only checks for existence of the prop. When `value` is defined, it checks if the actual value matches.
 
 :::note
 This matcher should be treated as an escape hatch to be used when all other matchers are not suitable.

website/docs/13.x/docs/api/queries.mdx

@@ -1,6 +1,6 @@
 # Queries
 
-Queries are one of the main building blocks for the React Native Testing Library. They enable you to find relevant elements in the element tree, which represents your application's user interface when running under tests.
+Queries are one of the main building blocks of React Native Testing Library. They let you find elements in the element tree, which represents your application's user interface when running under tests.
 
 ## Accessing queries
 
@@ -18,7 +18,7 @@ test('accessing queries using "screen" object', () => {
 })
 ```
 
-The modern and recommended way to access queries is to use the `screen` object exported by the `@testing-library/react-native` package. This object contains methods for all available queries bound to the most recently rendered UI.
+The recommended way to access queries is to use the `screen` object exported by `@testing-library/react-native`. It contains methods for all available queries bound to the most recently rendered UI.
 
 ### Using `render` result
 
@@ -35,19 +35,16 @@ The classic way is to capture query functions returned from the `render` functio
 
 ## Query parts
 
-Each query is composed of two parts: variant and predicate, which are separated by the `by` word in the middle of the name.
+Each query is composed of two parts: variant and predicate, separated by the word `by` in the middle.
 
-Consider the following query:
+Consider the query `getByRole()`:
 
-```
-getByRole()
-```
-
-For this query, `getBy*` is the query variant, and `*ByRole` is the predicate.
+- `getBy*` is the query variant
+- `*ByRole` is the predicate
 
 ## Query variant
 
-The query variants describe the expected number (and timing) of matching elements, so they differ in their return type.
+The query variants describe the expected number (and timing) of matching elements, so they differ in return type.
 
 | Variant                                         | Assertion                     | Return type                                | Is Async? |
 | ----------------------------------------------- | ----------------------------- | ------------------------------------------ | --------- |
@@ -130,7 +127,7 @@ When your `findBy*` and `findAllBy*` queries throw because they can't find match
 
 ## Query predicates
 
-_Note: most methods like this one return a [`ReactTestInstance`](https://reactjs.org/docs/test-renderer.html#testinstance) with following properties that you may be interested in:_
+_Note: most methods like this one return a [`ReactTestInstance`](https://reactjs.org/docs/test-renderer.html#testinstance) with the following properties that you may be interested in:_
 
 ```typescript
 type ReactTestInstance = {
@@ -169,7 +166,7 @@ getByRole(
 Returns a `ReactTestInstance` with matching `role` or `accessibilityRole` prop.
 
 :::info
-In order for `*ByRole` queries to match an element it needs to be considered an accessibility element:
+For `*ByRole` queries to match an element, it needs to be considered an accessibility element:
 
 1. `Text`, `TextInput` and `Switch` host elements are these by default.
 2. `View` host elements need an explicit [`accessible`](https://reactnative.dev/docs/accessibility#accessible) prop set to `true`
@@ -236,7 +233,7 @@ getByLabelText(
 Returns a `ReactTestInstance` with matching label:
 
 - either by matching [`aria-label`](https://reactnative.dev/docs/accessibility#aria-label)/[`accessibilityLabel`](https://reactnative.dev/docs/accessibility#accessibilitylabel) prop
-- or by matching text content of view referenced by [`aria-labelledby`](https://reactnative.dev/docs/accessibility#aria-labelledby-android)/[`accessibilityLabelledBy`](https://reactnative.dev/docs/accessibility#accessibilitylabelledby-android) prop
+- or by matching the text content of the view referenced by [`aria-labelledby`](https://reactnative.dev/docs/accessibility#aria-labelledby-android)/[`accessibilityLabelledBy`](https://reactnative.dev/docs/accessibility#accessibilitylabelledby-android) prop
 
 ```jsx
 import { render, screen } from '@testing-library/react-native';
@@ -284,7 +281,7 @@ getByDisplayValue(
 ): ReactTestInstance;
 ```
 
-Returns a `ReactTestInstance` for a `TextInput` with a matching display value—may be a string or regular expression.
+Returns a `ReactTestInstance` for a `TextInput` with a matching display value. The value can be a string or regular expression.
 
 ```jsx
 import { render, screen } from '@testing-library/react-native';
@@ -308,7 +305,7 @@ getByText(
 ): ReactTestInstance;
 ```
 
-Returns a `ReactTestInstance` with matching text—may be a string or regular expression.
+Returns a `ReactTestInstance` with matching text. The text can be a string or regular expression.
 
 This method joins `<Text>` siblings to find matches, similarly to [how React Native handles these components](https://reactnative.dev/docs/text#containers). This allows querying for strings that will be visually rendered together but may be semantically separate React components.
 

website/docs/14.x/docs/api/jest-matchers.mdx

@@ -40,7 +40,7 @@ expect(container).toContainElement(
 )
 ```
 
-Checks if a container element contains another host element.
+Checks if the container element contains another host element.
 
 ### `toBeEmptyElement()`
 
@@ -64,7 +64,7 @@ expect(element).toHaveDisplayValue(
 )
 ```
 
-Checks if a `TextInput` element has the specified display value. You can pass a `string` or `RegExp`, plus [text match options](/docs/api/queries#text-match-options) like `exact` and `normalizer`.
+Checks if the `TextInput` element has the specified display value. You can pass a `string` or `RegExp`, plus [text match options](/docs/api/queries#text-match-options) like `exact` and `normalizer`.
 
 ### `toHaveAccessibilityValue()`
 

website/docs/14.x/docs/api/queries.mdx

@@ -171,8 +171,8 @@ Returns a `HostElement` with matching `role` or `accessibilityRole` prop.
 :::info
 In order for `*ByRole` queries to match an element it needs to be considered an accessibility element:
 
-1. `Text`, `TextInput` and `Switch` host elements are these by default.
-2. `View` host elements need an explicit [`accessible`](https://reactnative.dev/docs/accessibility#accessible) prop set to `true`
+1. `Text`, `TextInput` and `Switch` elements are these by default.
+2. `View` elements need an explicit [`accessible`](https://reactnative.dev/docs/accessibility#accessible) prop set to `true`
 3. Some React Native composite components like `Pressable` & `TouchableOpacity` render host `View` element with `accessible` prop already set.
 
 :::