Apply suggestions from code review

Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>

Author: iritkatriel

Doc/reference/compound_stmts.rst

@@ -340,15 +340,15 @@ exceptions (:exc:`BaseExceptionGroup` instances). A :keyword:`try` statement
 can have either :keyword:`except` or :keyword:`!except*` clauses, but not both.
 The exception type for matching is mandatory in the case of :keyword:`!except*`,
 so ``except*:`` is a syntax error. The type is interpreted as in the case of
-:keyword:`except`, but matching is performed on the exceptions contained in the
+:keyword:`!except`, but matching is performed on the exceptions contained in the
 group that is being handled. An :exc:`TypeError` is raised if a matching
-type is a subclass of :exc:`BaseExceptionGroup`, because that would have
+type is a subclass of :exc:`!BaseExceptionGroup`, because that would have
 ambiguous semantics.
 
 When an exception group is raised in the try block, each :keyword:`!except*`
 clause splits (see :meth:`~BaseExceptionGroup.split`) it into the subgroups
 of matching and non-matching exceptions. If the matching subgroup is not empty,
-it becomes the handled exception (the value returned from ``sys.exception()``)
+it becomes the handled exception (the value returned from :func:`sys.exception`)
 and assigned to the target of the :keyword:`!except*` clause (if there is one).
 Then, the body of the :keyword:`!except*` clause executes. If the non-matching
 subgroup is not empty, it is processed by the next :keyword:`!except*` in the