docs: tweaks

Author: mdjastrzebski

website/docs/JestMatchers.md

@@ -81,10 +81,10 @@ expect(element).toHaveDisplayValue(
 
 This allows you to assert whether the given `TextInput` element has specified display value. It accepts either `string` or `RegExp` matchers, as well as [text match options](Queries.md#text-match-options) of `exact` and `normalizer`.
 
-### `toHaveAccessibleValue()`
+### `toHaveAccessibilityValue()`
 
 ```ts
-expect(element).toHaveAccessibleValue(
+expect(element).toHaveAccessibilityValue(
   value: {
     min?: number;
     max?: number;

website/docs/MigrationJestMatchers.md

@@ -3,7 +3,7 @@ id: migration-jest-native
 title: Migration from Jest Native matchers
 ---
 
-This guide describes steps necessary to migrate from [legacy Jest Native matchers](https://github.com/testing-library/jest-native) `v5` to [built-in Jest matchers](jest-matchers). 
+This guide describes steps necessary to migrate from [legacy Jest Native matchers v5](https://github.com/testing-library/jest-native) to [built-in Jest matchers](jest-matchers). 
 
 import TOCInline from '@theme/TOCInline';
 
@@ -50,15 +50,12 @@ Following matchers should work the same:
 * [`toBeOnTheScreen()`](jest-matchers#tobeonthescreen)
 * [`toBeVisible()`](jest-matchers#tobevisible)
 * [`toContainElement()`](jest-matchers#tocontainelement)
+* [`toHaveAccessibilityValue()`](jest-matchers#tohaveaccessibilityvalue)
 * [`toHaveDisplayValue()`](jest-matchers#tohavedisplayvalue)
 * [`toHaveProp()`](jest-matchers#tohaveprop)
 * [`toHaveStyle()`](jest-matchers#tohavestyle)
 * [`toHaveTextContent()`](jest-matchers#tohavetextcontent)
 
-### Renamed matchers
-
-`toHaveAccessibilityValue()` matcher has been renamed to [`toHaveAccessibleValue()`](jest-matchers#tohaveaccessiblevalue) but otherwise should work the same.
-
 ### Removed matchers
 
 `toHaveAccessibilityState()` matcher has been replaced by following matchers:
@@ -70,6 +67,13 @@ Following matchers should work the same:
 
 The new matchers support both `accessbililityState` and `aria-*` props.
 
+### Added matchers
+
+Following new matchers have been added:
+* [`toHaveAccessibleName()`](jest-matchers#tohaveaccessiblename)
+
+### Noteworthy details
+
 You should be aware of following changes:
 * [`toBeEnabled()` / `toBeDisabled()`](jest-matchers#tobeenabled) matchers also check the disabled state for element ancestors and not only the element itself
 * [`toBeChecked()`](jest-matchers#tobechecked) matcher supports only elements with `checkbox` or `radio` role