small wording changes

Author: jakkdl

changelog/10839.deprecation.rst

@@ -1 +1 @@
-Requesting an asynchronous fixture without a `pytest_fixture_setup` to handle it will now give a DeprecationWarning. This most commonly happens if a sync test requests an async fixture. This should have no effect on a majority of users with async tests or fixtures, but may affect non-standard hook setups or ``autouse=True``. For guidance on how to work around this warning see :ref:`sync-test-async-fixture`.
+Requesting an asynchronous fixture without a `pytest_fixture_setup` hook that resolves it will now give a DeprecationWarning. This most commonly happens if a sync test requests an async fixture. This should have no effect on a majority of users with async tests or fixtures using async pytest plugins, but may affect non-standard hook setups or ``autouse=True``. For guidance on how to work around this warning see :ref:`sync-test-async-fixture`.

src/_pytest/fixtures.py

@@ -961,7 +961,7 @@ def __init__(
         ids: tuple[object | None, ...] | Callable[[Any], object | None] | None = None,
         *,
         _ispytest: bool = False,
-        # only used to emit a deprecationwarning, can be removed in pytest9
+        # only used in a deprecationwarning msg, can be removed in pytest9
         _autouse: bool = False,
     ) -> None:
         check_ispytest(_ispytest)