Updated notes on forward references regarding instrumented code

Forward references still need to be resolved in some cases.

docs/userguide.rst

@@ -134,8 +134,10 @@ Notes on forward reference handling
 The internal type checking functions, injected to instrumented code by either
 :func:`@typechecked <typechecked>` or the import hook, use the "naked" versions of any
 annotations, undoing any quotations in them (and the effects of
-``from __future__ import annotations``). As such, the
-:attr:`~.TypeCheckConfiguration.forward_ref_policy` does not apply to instrumented code.
+``from __future__ import annotations``). As such, in instrumented code, the
+:attr:`~.TypeCheckConfiguration.forward_ref_policy` only applies when using type
+variables containing forward references, or type aliases likewise containing forward
+references.
 
 To facilitate the use of types only available to static type checkers, Typeguard
 recognizes module-level imports guarded by ``if typing.TYPE_CHECKING:`` or

src/typeguard/_config.py

@@ -76,10 +76,6 @@ class TypeCheckConfiguration:
 
          Specifies what to do when a forward reference fails to resolve.
 
-         Note that this setting only applies to :func:`.check_type`, as instrumented
-         code eagerly resolves forward references during compilation. See the
-         :ref:`forwardrefs` section in the documentation for further information.
-
          Default: ``WARN``
 
     .. attribute:: collection_check_strategy