Fix minor typos (#78294)

Signed-off-by: Hu Shuai <hus.fnst@fujitsu.com>

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

@@ -203,7 +203,7 @@ Publishing the collection
   * Whether to add ignore entries to the corresponding ``tests/sanity/ignore-*.txt`` file and create issues, for example for removed features in ``modules/plugins``.
 
   Once the CI tests pass, merge the pull request. Make sure that this pull request is merged not too much later after the release
-  for ``verison_added`` sanity tests not to expect the wrong version for the new feature pull request.
+  for ``version_added`` sanity tests not to expect the wrong version for the new feature pull request.
 
 .. note::
 

docs/docsite/rst/community/maintainers_workflow.rst

@@ -52,7 +52,7 @@ Collection maintainers are responsible for releasing new versions of a collectio
 #. Planning and announcement.
 #. Generating a changelog.
 #. Creating a release git tag and pushing it.
-#. Automaticly publishing the release tarball on `Ansible Galaxy <https://galaxy.ansible.com/>`_ through the `Zuul dashboard <https://dashboard.zuul.ansible.com/t/ansible/builds?pipeline=release>`_.
+#. Automatically publishing the release tarball on `Ansible Galaxy <https://galaxy.ansible.com/>`_ through the `Zuul dashboard <https://dashboard.zuul.ansible.com/t/ansible/builds?pipeline=release>`_.
 #. Final announcement.
 #. Optionally, `file a request to include a new collection into the Ansible package <https://github.com/ansible-collections/ansible-inclusion>`_.