address mistyping detected by codespell checker. (backport #4980) (#4982)

* address mistyping detected by codespell checker. (#4980)

Signed-off-by: Tomoya Fujita <Tomoya.Fujita@sony.com>
(cherry picked from commit 49f66fd)

Signed-off-by: Alejandro Hernandez Cordero <ahcorde@gmail.com>
Co-authored-by: Tomoya Fujita <Tomoya.Fujita@sony.com>
Co-authored-by: Alejandro Hernandez Cordero <ahcorde@gmail.com>

Author: 3 people

source/Concepts/Basic/About-Interfaces.rst

@@ -207,7 +207,7 @@ For example:
 Constants
 ^^^^^^^^^
 
-Each constant definition is like a field description with a default value, except that this value can never be changed programatically.
+Each constant definition is like a field description with a default value, except that this value can never be changed programmatically.
 This value assignment is indicated by use of an equal '=' sign, e.g.
 
 .. code-block:: bash

source/Concepts/Basic/About-Topics.rst

@@ -14,7 +14,7 @@ Publish/Subscribe
 -----------------
 
 A publish/subscribe system is one in which there are producers of data (publishers) and consumers of data (subscribers).
-The publishers and subscribers know how to contact each other through the concept of a "topic", which is a common name so that the entites can find each other.
+The publishers and subscribers know how to contact each other through the concept of a "topic", which is a common name so that the entities can find each other.
 For instance, when you create a publisher, you must also give it a string that is the name of the topic; the same goes for the subscriber.
 Any publishers and subscribers that are on the same topic name can directly communicate with each other.
 There may be zero or more publishers and zero or more subscribers on any particular topic.

source/Concepts/Intermediate/About-RQt.rst

@@ -56,7 +56,7 @@ RQt Components Structure
 
 RQt consists of two metapackages:
 
-* *rqt* - core infrastucture modules.
+* *rqt* - core infrastructure modules.
 * *rqt_common_plugins* - Commonly useful debugging tools.
 
 Advantage of RQt framework
@@ -72,7 +72,7 @@ Compared to building your own GUIs from scratch:
 From system architecture's perspective:
 
 * Support multi-platform (basically wherever `QT <http://qt-project.org/>`__ and ROS run) and multi-language (``Python``, ``C++``).
-* Manageable lifecycle: RQt plugins using a common API makes maintainance & reuse easier.
+* Manageable lifecycle: RQt plugins using a common API makes maintenance & reuse easier.
 
 
 Further Reading

source/How-To-Guides/Ament-CMake-Documentation.rst

@@ -341,7 +341,7 @@ The macros have additional parameters:
 
     find_package(ament_cmake_gtest REQUIRED)
     ament_add_gtest(some_test <test_sources>
-      APPEND_ENV PATH=some/addtional/path/for/testing/resources)
+      APPEND_ENV PATH=some/additional/path/for/testing/resources)
 
 - ``APPEND_LIBRARY_DIRS``: append libraries so that they can be found by the linker at runtime.
   This can be achieved by setting environment variables like ``PATH`` on Windows and ``LD_LIBRARY_PATH`` on Linux, but this makes the call platform specific.

source/How-To-Guides/Core-maintainer-guide.rst

@@ -6,7 +6,7 @@
 ROS 2 Core Maintainer Guide
 ===========================
 
-Each package in the ROS 2 core has one or more maintainers that are responsibile for the general health of the package.
+Each package in the ROS 2 core has one or more maintainers that are responsible for the general health of the package.
 This guide gives some information about the responsibilities of a ROS 2 core package maintainer.
 
 .. contents:: Table of Contents

source/How-To-Guides/Getting-Backtraces-in-ROS-2.rst

@@ -232,7 +232,7 @@ We will insert the GDB snippet here.
 
   prefix=['xterm -e gdb -ex run --args']
 
-This will provide a more interactive debbuging experience.
+This will provide a more interactive debugging experience.
 Example usecase for debugging building upon ``'start_sync_slam_toolbox_node'`` -
 
 .. code-block:: python

source/How-To-Guides/Installation-Troubleshooting.rst

@@ -51,7 +51,7 @@ then you will need to update your firewall configuration to allow multicast usin
    sudo ufw allow in proto udp from 224.0.0.0/4
 
 
-You can check if the multicast flag is enabled for your network interface using the :code:`ifconfig` tool and looking for :code:`MULITCAST` in the flags section:
+You can check if the multicast flag is enabled for your network interface using the :code:`ifconfig` tool and looking for :code:`MULTICAST` in the flags section:
 
 .. code-block:: bash
 
@@ -218,7 +218,7 @@ To resolve this error, you will need to:
 
 rosdep install error ``homebrew: Failed to detect successful installation of [qt5]``
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-While following the :doc:`Creating a workspace <../Tutorials/Beginner-Client-Libraries/Creating-A-Workspace/Creating-A-Workspace>` tutorial, you might encounter the following error stating that ``rosdep`` failes to install Qt5.
+While following the :doc:`Creating a workspace <../Tutorials/Beginner-Client-Libraries/Creating-A-Workspace/Creating-A-Workspace>` tutorial, you might encounter the following error stating that ``rosdep`` fails to install Qt5.
 
 .. code-block:: bash
 

source/How-To-Guides/Migrating-from-ROS1/Migrating-CPP-Packages.rst

@@ -109,7 +109,7 @@ If your ``CMakeLists.txt`` uses ``include_directories()``, then delete those cal
    # Delete calls to include_directories like this one!
    include_directories(include ${catkin_INCLUDE_DIRS})
 
-Add a call ``target_include_directories()`` for every library in your pacakage (`example <https://github.com/ros2/geometry2/blob/d85102217f692746abea8546c8e41f0abc95c8b8/tf2/CMakeLists.txt#L24-L26>`__).
+Add a call ``target_include_directories()`` for every library in your package (`example <https://github.com/ros2/geometry2/blob/d85102217f692746abea8546c8e41f0abc95c8b8/tf2/CMakeLists.txt#L24-L26>`__).
 
 .. code-block:: cmake
 

source/How-To-Guides/Migrating-from-ROS1/Migrating-Launch-Files.rst

@@ -314,7 +314,7 @@ New tags in ROS 2
 set_env and unset_env
 ^^^^^^^^^^^^^^^^^^^^^
 
-See `env`_ tag decription.
+See `env`_ tag description.
 
 push_ros_namespace
 ^^^^^^^^^^^^^^^^^^

source/How-To-Guides/Migrating-from-ROS1/Migrating-Python-Package-Example.rst

@@ -485,7 +485,7 @@ Remove the statement that imports ``rospy``.
     # Remove this
     import rospy
 
-Rplace it with a statement that imports ``rclpy``.
+Replace it with a statement that imports ``rclpy``.
 
 .. code-block:: Python
 
@@ -807,7 +807,7 @@ Echo the message published by the node in the third terminal:
 
 You should see messages with the current time being published in the second terminal, and those same messages received in the third.
 
-Refactor code to use ROS 2 convensions
+Refactor code to use ROS 2 conventions
 --------------------------------------
 
 You have successfully migrated a ROS 1 Python package to ROS 2!