python
diff --git a/‎Doc/library/importlib.rst
Copy file name to clipboardExpand all lines: Doc/library/importlib.rst
+2-2Lines changed: 2 additions & 2 deletions b/‎Doc/library/importlib.rst
Copy file name to clipboardExpand all lines: Doc/library/importlib.rst
+2-2Lines changed: 2 additions & 2 deletions
diff --git a/‎Doc/library/logging.rst
Copy file name to clipboardExpand all lines: Doc/library/logging.rst
+1-1Lines changed: 1 addition & 1 deletion b/‎Doc/library/logging.rst
Copy file name to clipboardExpand all lines: Doc/library/logging.rst
+1-1Lines changed: 1 addition & 1 deletion
@@ -1252,7 +1252,7 @@ find and load modules.
    be only a single binary per framework, and there can be no executable binary
    material outside the Frameworks folder.
 
-   To accomodate this requirement, when running on iOS, extension module
+   To accommodate this requirement, when running on iOS, extension module
    binaries are *not* packaged as ``.so`` files on ``sys.path``, but as
    individual standalone frameworks. To discover those frameworks, this loader
    is be registered against the ``.fwork`` file extension, with a ``.fwork``
@@ -1279,7 +1279,7 @@ find and load modules.
 
    When a module is loaded with this loader, the ``__file__`` for the module
    will report as the location of the ``.fwork`` file. This allows code to use
-   the ``__file__`` of a  module as an anchor for file system traveral.
+   the ``__file__`` of a  module as an anchor for file system traversal.
    However, the spec origin will reference the location of the *actual* binary
    in the ``.framework`` folder.
 
 
@@ -1204,7 +1204,7 @@ functions.
    most programs will want to carefully and explicitly control the logging
    configuration, and should therefore prefer creating a module-level logger and
    calling :meth:`Logger.debug` (or other level-specific methods) on it, as
-   described at the beginnning of this documentation.
+   described at the beginning of this documentation.
 
 
 .. function:: info(msg, *args, **kwargs)