[skip ci] Minor edits.

rwgk · rwgk · commit 41290e150d40 · 2025-06-16T22:32:18.000-07:00
diff --git a/docs/advanced/exceptions.rst b/docs/advanced/exceptions.rst
@@ -329,22 +329,22 @@ Any Python error must be thrown or cleared, or Python/pybind11 will be left in
 an invalid state.
 
 Handling warnings from the Python C API
-=====================================
+=======================================
 
-Wrappers for handling Python warnings are implemented in ``pybind11/warnings.h``,
-which means that ``#include`` must be added explicitly (in other words, it is not
-transitively included with ``pybind11/pybind11.h``).
+Wrappers for handling Python warnings are provided in ``pybind11/warnings.h``.
+This header must be included explicitly; it is not transitively included via
+``pybind11/pybind11.h``.
 
 Warnings can be raised with the ``warn`` function:
 
 .. code-block:: cpp
 
-    py::warnings::warn("This is warning!", PyExc_Warning);
+    py::warnings::warn("This is a warning!", PyExc_Warning);
 
-    // Optionally, `stack_level` can be specified.
+    // Optionally, a `stack_level` can be specified.
     py::warnings::warn("Another one!", PyExc_DeprecationWarning, 3);
 
-New warning types can be registered on the module level with ``new_warning_type``:
+New warning types can be registered at the module level using ``new_warning_type``:
 
 .. code-block:: cpp
 
