docs: fix typos (#79082)

docs/docsite/rst/community/collection_contributors/collection_integration_add.rst

@@ -36,7 +36,7 @@ We should basically do the following:
 
 1. Clone the collection to the ``~/ansible_collections/community.abstract`` directory on your local machine.
 
-2. From the ``~/ansble_collections/community.abstract`` directory, create directories for the ``setup`` target:
+2. From the ``~/ansible_collections/community.abstract`` directory, create directories for the ``setup`` target:
 
 .. code-block:: bash
 
@@ -63,7 +63,7 @@ This is a very simplified example.
 
 4. Add the target for the module you are testing.
 
-Let's say the module is called ``abstact_service_info``. Create the following directory structure in the target:
+Let's say the module is called ``abstract_service_info``. Create the following directory structure in the target:
 
 .. code-block:: bash
 
@@ -90,7 +90,7 @@ Add the following to ``tests/integration/targets/abstract_service_info/tasks/mai
 .. code-block:: yaml
 
   - name: Fetch info from abstract service
-    anstract_service_info:
+    abstract_service_info:
       host: 127.0.0.1  # We assume the service accepts local connection by default
       port: 1234       # We assume that the service is listening this port by default
     register: result   # This variable will contain the returned JSON including the server version

docs/docsite/rst/community/collection_contributors/collection_release_with_branches.rst

@@ -213,7 +213,7 @@ Publishing the collection
 Releasing patch versions
 -------------------------
 
-The new version is assumed to be ``X.Y.Z``, and the previous patch version is assumed to be ``X.Y.z`` with ``z < Z``.  ``z`` is frequently``0`` snce patch releases are uncommon.
+The new version is assumed to be ``X.Y.Z``, and the previous patch version is assumed to be ``X.Y.z`` with ``z < Z``.  ``z`` is frequently``0`` since patch releases are uncommon.
 
 Releasing when more minor versions are expected
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

docs/docsite/rst/community/contributor_path.rst

@@ -48,7 +48,7 @@ You should understand at least *basics* of the following tools:
 You can learn these tools more in depth when working on your first contributions.
 
 
-Each Ansible project has its own set of contributor guidelines. Familarize yourself with these as you prepare your first contributions.
+Each Ansible project has its own set of contributor guidelines. Familiarize yourself with these as you prepare your first contributions.
 
 * :ref:`Ansible Core development <developer_guide>`.
 * :ref:`Ansible collection development <developing_collections>` and the collection-level contributor guidelines in the collection repository.
@@ -72,7 +72,7 @@ See :ref:`communication` for ways to communicate and engage with the Ansible com
 Teach others
 ============
 
-Share your experience with other contributors through `improving documentation <ommunity_documentation_contributions>`, answering question from other contributors and users  on `Matrix/Libera.Chat IRC <communicate>`, giving advice in issues and pull requests, and discussing the `Community Topics <https://github.com/ansible-community/community-topics/issues>`_.
+Share your experience with other contributors through `improving documentation <community_documentation_contributions>`, answering question from other contributors and users  on `Matrix/Libera.Chat IRC <communicate>`, giving advice in issues and pull requests, and discussing the `Community Topics <https://github.com/ansible-community/community-topics/issues>`_.
 
 Become a collection maintainer
 ===============================

docs/docsite/rst/dev_guide/developing_python_3.rst

@@ -89,7 +89,7 @@ and while Python 2 is not a concern anymore we will continue to use them as they
 dealing with unicode problematic.
 
 While we will not be using it most of it anymore, the documentation below is still useful for those developing modules
-that still need to support both Python 2 and 3 simultaneouslly.
+that still need to support both Python 2 and 3 simultaneously.
 
 Unicode Sandwich common borders: places to convert bytes to text in controller code
 -----------------------------------------------------------------------------------