docs: final tweaks

Author: mdjastrzebski

website/docs/EslintPLluginTestingLibrary.md

@@ -6,8 +6,6 @@ title: ESLint Plugin Testing Library Compatibility
 
 Most of the rules of the [eslint-plugin-testing-library](https://github.com/testing-library/eslint-plugin-testing-library) are compatible with this library except the followings:
 
-- [prefer-screen-queries](https://github.com/testing-library/eslint-plugin-testing-library/blob/main/docs/rules/prefer-screen-queries.md): there is no screen object so this rule shouldn't be used
-
 - [prefer-user-event](https://github.com/testing-library/eslint-plugin-testing-library/blob/main/docs/rules/prefer-user-event.md): userEvent requires a dom environement so it is not compatible with this library
 
 Also, some rules have become useless, unless maybe you're using an old version of the library:

website/docs/FAQ.md

@@ -31,3 +31,15 @@ The the negative side:
 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.
 
 </details>
+
+<details>
+  <summary>Should I use/migrate to `screen` queries?</summary>
+
+<br />
+
+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.
+
+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.
+
+</details>