before_mapper_configured event doc fixes (#12200)

* Remove spurious word in before_mapper_configured event doc

* Fix reST markup in before_mapper_configured event doc

(cherry picked from commit c6be0c1f205cf83467d68eb40fb650b9274519f9)

diff --git a/lib/sqlalchemy/orm/events.py b/lib/sqlalchemy/orm/events.py
index 959ad01043ce22cd32b0d088c06772935b85d6d5..d2ae616371d647426d84076aecb339db274d066c 100644 (file)
--- a/lib/sqlalchemy/orm/events.py
+++ b/lib/sqlalchemy/orm/events.py
@@ -986,7 +986,7 @@ class MapperEvents(event.Events[mapperlib.Mapper[Any]]):
         symbol which indicates to the :func:`.configure_mappers` call that this
         particular mapper (or hierarchy of mappers, if ``propagate=True`` is
         used) should be skipped in the current configuration run. When one or
-        more mappers are skipped, the he "new mappers" flag will remain set,
+        more mappers are skipped, the "new mappers" flag will remain set,
         meaning the :func:`.configure_mappers` function will continue to be
         called when mappers are used, to continue to try to configure all
         available mappers.
@@ -995,7 +995,7 @@ class MapperEvents(event.Events[mapperlib.Mapper[Any]]):
         :meth:`.MapperEvents.before_configured`,
         :meth:`.MapperEvents.after_configured`, and
         :meth:`.MapperEvents.mapper_configured`, the
-        :meth;`.MapperEvents.before_mapper_configured` event provides for a
+        :meth:`.MapperEvents.before_mapper_configured` event provides for a
         meaningful return value when it is registered with the ``retval=True``
         parameter.