docs: v14 tweaks

website/docs/12.x/index.md

@@ -2,18 +2,17 @@
 pageType: home
 
 hero:
-  name: 'React Native'
-  text: 'Testing Library'
+  name: 'React Native Testing Library'
   image:
     src: /img/owl.png
   tagline: Helps you to write better tests with less effort.
   actions:
     - theme: brand
       text: Quick Start
-      link: /docs/start/quick-start
+      link: /12.x/docs/start/quick-start
     - theme: alt
       text: Explore API
-      link: /docs/api
+      link: /12.x/docs/api
 features:
   - title: Maintainable
     details: Write maintainable tests for your React Native apps.

website/docs/13.x/index.md

@@ -2,8 +2,7 @@
 pageType: home
 
 hero:
-  name: 'React Native'
-  text: 'Testing Library'
+  name: 'React Native Testing Library'
   image:
     src: /img/owl.png
   tagline: Helps you to write better tests with less effort.

website/docs/14.x/docs/_meta.json

@@ -14,11 +14,5 @@
     "type": "dir",
     "name": "advanced",
     "label": "Advanced Guides"
-  },
-  {
-    "type": "dir",
-    "name": "migration",
-    "label": "Migration Guides",
-    "collapsed": true
   }
 ]

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

@@ -6,10 +6,6 @@ This guide describes built-in Jest matchers, we recommend using these matchers a
 
 There is no need to set up the built-in matchers; they are automatically available in your tests when you import anything from `@testing-library/react-native`, e.g., `render`.
 
-## Migration from legacy Jest Native matchers.
-
-If you are already using legacy Jest Native matchers we have a [migration guide](/docs/migration/jest-matchers) for moving to the built-in matchers.
-
 ## Checking element existence
 
 ### `toBeOnTheScreen()`