doc improvements after review

Author: jakkdl

doc/en/how-to/assert.rst

@@ -279,12 +279,12 @@ exception at a specific level; exceptions contained directly in the top
         assert not excinfo.group_contains(RuntimeError, depth=2)
         assert not excinfo.group_contains(TypeError, depth=1)
 
-Alternate form (legacy)
-~~~~~~~~~~~~~~~~~~~~~~~
+Alternate `pytest.raises` form (legacy)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-There is an alternate form where you pass
-a function that will be executed, along ``*args`` and ``**kwargs``, and :func:`pytest.raises`
-will execute the function with the arguments and assert that the given exception is raised:
+There is an alternate form of :func:`pytest.raises` where you pass
+a function that will be executed, along with ``*args`` and ``**kwargs``. :func:`pytest.raises`
+will then execute the function with those arguments and assert that the given exception is raised:
 
 .. code-block:: python
 
@@ -329,6 +329,18 @@ This will only "xfail" if the test fails by raising ``IndexError`` or subclasses
 * Using :func:`pytest.raises` is likely to be better for cases where you are
   testing exceptions your own code is deliberately raising, which is the majority of cases.
 
+You can also use :class:`pytest.RaisesGroup`:
+
+.. code-block:: python
+
+    def f():
+        raise ExceptionGroup("", [IndexError()])
+
+
+    @pytest.mark.xfail(raises=RaisesGroup(IndexError))
+    def test_f():
+        f()
+
 
 .. _`assertwarns`:
 

src/_pytest/_raises_group.py renamed to src/_pytest/raises_group.py

@@ -197,9 +197,6 @@ class RaisesExc(AbstractRaises[BaseExcT_co_default]):
             ...
         with RaisesGroups(RaisesExc(check=lambda x: type(x) is ValueError)):
             ...
-
-    Tip: if you install ``hypothesis`` and import it in ``conftest.py`` you will get
-    readable ``repr``'s of ``check`` callables in the output.
     """
 
     # Trio bundled hypothesis monkeypatching, we will probably instead assume that
@@ -367,8 +364,13 @@ class RaisesGroup(AbstractRaises[BaseExceptionGroup[BaseExcT_co]]):
     even though it generally does not care about the order of the exceptions in the group.
     To avoid the above you should specify the first :exc:`ValueError` with a :class:`RaisesExc` as well.
 
-    Tip: if you install ``hypothesis`` and import it in ``conftest.py`` you will get
-    readable ``repr``'s of ``check`` callables in the output.
+    .. note::
+        When raised exceptions don't match the expected ones, you'll get a detailed error
+        message explaining why. This includes ``repr(check)`` if set, which in Python can be
+        overly verbose, showing memory locations etc etc.
+
+        If installed and imported (in e.g. ``conftest.py``), the ``hypothesis`` library will
+        monkeypatch this output to provide shorter & more readable repr's.
     """
 
     # allow_unwrapped=True requires: singular exception, exception not being