docs: improve wording in FAQ

Author: Rel1cx

apps/website/content/docs/faq.mdx

@@ -14,7 +14,7 @@ Although you can use it with other renderers, it will always assume that you are
 
 Unfortunately, the maintainers of `eslint-plugin-react` refuse to change that[⁴].
 
-Just as in [Beyond the DOM](https://legacy.reactjs.org/docs/design-principles.html#beyond-the-dom) we believe that the community will benefit from a renderer-agnostic and x-platform-supported plugin. This is also the initial motivation for creating `eslint-react`.
+Just as in [Beyond the DOM](https://legacy.reactjs.org/docs/design-principles.html#beyond-the-dom) we believe the future of React Linter is not limited to the DOM. This influences every decision made in `eslint-react`, and it is the reason why we created it.
 
 </Accordion>
 

packages/plugins/eslint-plugin-react-x/src/rules/no-implicit-key.md

@@ -31,7 +31,7 @@ Prevents `key` from not being explicitly specified (e.g. spreading `key` from ob
 
 This makes it hard to see if the key was passed correctly to the element or where it came from.
 
-And it's also be proposed to be deprecated is this RFC: [Deprecate spreading key from objects](https://github.com/reactjs/rfcs/pull/107#issue-413235149)
+And it's also be proposed to be deprecated is this RFC: [Deprecate spreading key from objects](https://github.com/reactjs/rfcs/pull/107#issue-413235149).
 
 ## Examples