docs: suspense docs

Author: mdjastrzebski

website/docs/13.x/docs/api/events/fire-event.mdx

@@ -1,8 +1,6 @@
 # Fire Event API
 
-```ts
-function fireEvent(element: ReactTestInstance, eventName: string, ...data: unknown[]): void;
-```
+## `fireEvent` {#fire-event}
 
 :::note
 For common events like `press` or `type` it's recommended to use [User Event API](docs/api/events/user-event) as it offers
@@ -11,6 +9,10 @@ more realistic event simulation by emitting a sequence of events with proper eve
 Use Fire Event for cases not supported by User Event and for triggering event handlers on composite components.
 :::
 
+```ts
+function fireEvent(element: ReactTestInstance, eventName: string, ...data: unknown[]): void;
+```
+
 The `fireEvent` API allows you to trigger all kinds of event handlers on both host and composite components. It will try to invoke a single event handler traversing the component tree bottom-up from passed element and trying to find enabled event handler named `onXxx` when `xxx` is the name of the event passed.
 
 Unlike User Event, this API does not automatically pass event object to event handler, this is responsibility of the user to construct such object.
@@ -57,14 +59,17 @@ FireEvent exposes convenience methods for common events like: `press`, `changeTe
 
 ### `fireEvent.press` {#press}
 
-```
-fireEvent.press: (element: ReactTestInstance, ...data: Array<any>) => void
-```
-
 :::note
 It is recommended to use the User Event [`press()`](docs/api/events/user-event#press) helper instead as it offers more realistic simulation of press interaction, including pressable support.
 :::
 
+```tsx
+fireEvent.press: (
+  element: ReactTestInstance,
+  ...data: Array<any>,
+) => void
+```
+
 Invokes `press` event handler on the element or parent element in the tree.
 
 ```jsx
@@ -93,14 +98,17 @@ expect(onPressMock).toHaveBeenCalledWith(eventData);
 
 ### `fireEvent.changeText` {#change-text}
 
-```
-fireEvent.changeText: (element: ReactTestInstance, ...data: Array<any>) => void
-```
-
 :::note
 It is recommended to use the User Event [`type()`](docs/api/events/user-event#type) helper instead as it offers more realistic simulation of text change interaction, including key-by-key typing, element focus, and other editing events.
 :::
 
+```tsx
+fireEvent.changeText: (
+  element: ReactTestInstance,
+  ...data: Array<any>,
+) => void
+```
+
 Invokes `changeText` event handler on the element or parent element in the tree.
 
 ```jsx
@@ -121,8 +129,15 @@ fireEvent.changeText(screen.getByPlaceholderText('Enter data'), CHANGE_TEXT);
 
 ### `fireEvent.scroll` {#scroll}
 
-```
-fireEvent.scroll: (element: ReactTestInstance, ...data: Array<any>) => void
+:::note
+Prefer using [`user.scrollTo`](docs/api/events/user-event#scrollto) over `fireEvent.scroll` for `ScrollView`, `FlatList`, and `SectionList` components. User Event provides a more realistic event simulation based on React Native runtime behavior.
+:::
+
+```tsx
+fireEvent.scroll: (
+  element: ReactTestInstance,
+  ...data: Array<any>,
+) => void
 ```
 
 Invokes `scroll` event handler on the element or parent element in the tree.
@@ -152,12 +167,10 @@ fireEvent.scroll(screen.getByText('scroll-view'), eventData);
 ```
 
 :::note
-
 Prefer using [`user.scrollTo`](docs/api/events/user-event#scrollto) over `fireEvent.scroll` for `ScrollView`, `FlatList`, and `SectionList` components. User Event provides a more realistic event simulation based on React Native runtime behavior.
-
 :::
 
-## `fireEventAsync`
+## `fireEventAsync` {#async}
 
 :::info RNTL minimal version
 
@@ -190,24 +203,45 @@ Like `fireEvent`, `fireEventAsync` also provides convenience methods for common
 
 ### `fireEventAsync.press` {#async-press}
 
-```
-fireEventAsync.press: (element: ReactTestInstance, ...data: Array<any>) => Promise<unknown>
+:::note
+It is recommended to use the User Event [`press()`](docs/api/events/user-event#press) helper instead as it offers more realistic simulation of press interaction, including pressable support.
+:::
+
+```tsx
+fireEventAsync.press: (
+  element: ReactTestInstance,
+  ...data: Array<any>,
+) => Promise<unknown>
 ```
 
-Async version of `fireEvent.press` designed for React 19 and React Suspense. Use when press event handlers trigger suspense boundaries.
+Async version of `fireEvent.press` designed for React 19 and React Suspense. Use when `press` event handlers trigger suspense boundaries.
 
 ### `fireEventAsync.changeText` {#async-change-text}
 
-```
-fireEventAsync.changeText: (element: ReactTestInstance, ...data: Array<any>) => Promise<unknown>
+:::note
+It is recommended to use the User Event [`type()`](docs/api/events/user-event#type) helper instead as it offers more realistic simulation of text change interaction, including key-by-key typing, element focus, and other editing events.
+:::
+
+```tsx
+fireEventAsync.changeText: (
+  element: ReactTestInstance,
+  ...data: Array<any>,
+) => Promise<unknown>
 ```
 
-Async version of `fireEvent.changeText` designed for React 19 and React Suspense. Use when changeText event handlers trigger suspense boundaries.
+Async version of `fireEvent.changeText` designed for React 19 and React Suspense. Use when `changeText` event handlers trigger suspense boundaries.
 
 ### `fireEventAsync.scroll` {#async-scroll}
 
-```
-fireEventAsync.scroll: (element: ReactTestInstance, ...data: Array<any>) => Promise<unknown>
+:::note
+Prefer using [`user.scrollTo`](docs/api/events/user-event#scrollto) over `fireEventAsync.scroll` for `ScrollView`, `FlatList`, and `SectionList` components. User Event provides a more realistic event simulation based on React Native runtime behavior.
+:::
+
+```tsx
+fireEventAsync.scroll: (
+  element: ReactTestInstance,
+  ...data: Array<any>,
+) => Promise<unknown>
 ```
 
-Async version of `fireEvent.scroll` designed for React 19 and React Suspense. Use when scroll event handlers trigger suspense boundaries.
+Async version of `fireEvent.scroll` designed for React 19 and React Suspense. Use when `scroll` event handlers trigger suspense boundaries.

website/docs/13.x/docs/api/events/user-event.mdx

@@ -226,10 +226,6 @@ Events will not be emitted if the `editable` prop is set to `false`.
 
 ## `scrollTo()` \{#scroll-to}
 
-:::note
-`scrollTo` interaction has been introduced in RNTL v12.4.0.
-:::
-
 ```ts
 scrollTo(
   element: ReactTestInstance,

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

@@ -1,5 +1,7 @@
 # `render` function
 
+## `render`
+
 ```jsx
 function render(
   component: React.Element<any>,
@@ -20,32 +22,32 @@ test('basic test', () => {
 
 > When using React context providers, like Redux Provider, you'll likely want to wrap rendered component with them. In such cases, it's convenient to create your own custom `render` method. [Follow this great guide on how to set this up](https://testing-library.com/docs/react-testing-library/setup#custom-render).
 
-## Options
+### Options
 
 The behavior of the `render` method can be customized by passing various options as a second argument of the `RenderOptions` type:
 
-### `wrapper` option
+#### `wrapper`
 
 ```ts
 wrapper?: React.ComponentType<any>,
 ```
 
 This option allows you to wrap the tested component, passed as the first option to the `render()` function, in an additional wrapper component. This is useful for creating reusable custom render functions for common React Context providers.
 
-### `concurrentRoot` option {#concurrent-root}
+#### `concurrentRoot` {#concurrent-root}
 
 Set to `false` to disable concurrent rendering.
 Otherwise, `render` will default to using concurrent rendering used in the React Native New Architecture.
 
-### `createNodeMock` option
+#### `createNodeMock` {#create-node-mock}
 
 ```ts
 createNodeMock?: (element: React.Element) => unknown,
 ```
 
 This option allows you to pass `createNodeMock` option to `ReactTestRenderer.create()` method in order to allow for custom mock refs. You can learn more about this option from [React Test Renderer documentation](https://reactjs.org/docs/test-renderer.html#ideas).
 
-### `unstable_validateStringsRenderedWithinText` option
+#### `unstable_validateStringsRenderedWithinText`
 
 ```ts
 unstable_validateStringsRenderedWithinText?: boolean;
@@ -59,7 +61,7 @@ This **experimental** option allows you to replicate React Native behavior of th
 
 React Test Renderer does not enforce this check; hence, by default, React Native Testing Library also does not check this. That might result in runtime errors when running your code on a device, while the code works without errors in tests.
 
-## Result
+### Result
 
 The `render` function returns the same queries and utilities as the [`screen`](docs/api/screen) object. We recommended using the `screen` object as more developer-friendly way.