docs(prefer-explicit-assert): remove references to old rule (#78)

Author: Belco90

docs/rules/prefer-explicit-assert.md

@@ -13,12 +13,6 @@ elements in their tests rather than just use `getBy*` queries and expect
 it doesn't throw an error so it's easier to understand what's the
 expected behavior within the test.
 
-> ⚠️ Please note that this rule is recommended to be used together with
-> [prefer-expect-query-by](docs/rules/prefer-expect-query-by.md), so the
-> combination of these two rules will force users to do 2 actual
-> changes: wrap `getBy*` with `expect` assertion and then use `queryBy*`
-> instead of `getBy*` for asserting.
-
 Examples of **incorrect** code for this rule:
 
 ```js
@@ -41,9 +35,6 @@ expect(getByText('foo')).toBeDefined();
 const utils = render(<Component />);
 expect(utils.getByText('foo')).toBeDefined();
 
-// ⚠️ `getBy*` should be replaced by `queryBy*` when combined with `prefer-expect-query-by` rule
-expect(queryByText('foo')).toBeDefined();
-
 // even more explicit if you use `@testing-library/jest-dom` matcher
 // for checking the element is present in the document
 expect(queryByText('foo')).toBeInTheDocument();
@@ -74,10 +65,6 @@ This rule accepts a single options argument:
 If you prefer to use `getBy*` queries implicitly as an assert-like
 method itself, then this rule is not recommended.
 
-## Related Rules
-
-- [prefer-expect-query-by](prefer-expect-query-by.md)
-
 ## Further Reading
 
 - [getBy query](https://testing-library.com/docs/dom-testing-library/api-queries#getby)