collection_requirements: fix typo (#1684)

* collection_requirements: fix typo * Update docs/docsite/rst/community/collection_contributors/collection_requirements.rst Co-authored-by: Don Naro <[email protected]> --------- Co-authored-by: Don Naro <[email protected]> (cherry picked from commit 6c7f7b5)
ansible · Jul 11, 2024 · d8d9e92 · d8d9e92
1 parent 92fec4b
commit d8d9e92
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/docsite/rst/community/collection_contributors/collection_requirements.rst b/docs/docsite/rst/community/collection_contributors/collection_requirements.rst
@@ -299,7 +299,7 @@ There are several types of content in collections which licensing has to address
 * The content that MUST be licensed with a free software license that is **compatible with** the `GPL-3.0-or-later <https://www.gnu.org/licenses/gpl-3.0-standalone.html>`_:
 
   * The ``modules/`` directory content.
-  * The ``module_utils/`` directory content: ansible-core itself typically uses the `BSD-2-clause <https://opensource.org/licenses/BSD-2-Clause>`_ license to make it possible for third-party modules which are licensed incompatibly with the GPLv3 to use them.Please consider this use case when licensing your own ``module_utils``.
+  * The ``module_utils/`` directory content: ansible-core typically uses the `BSD-2-clause <https://opensource.org/licenses/BSD-2-Clause>`_ license to allow third-party modules to use the ``module_utils`` in cases when those third-party modules have licenses that are incompatible with the GPLv3. Please consider this use case when licensing your own ``module_utils``.
   * Code outside ``plugins/``: if it DOES NOT import code licensed under ``GPL-3.0-or-later`` it may be licensed under another license compatible with ``GPL-3.0-or-later``.
   * Non-code content.
   * To be allowed, the license MUST be considered open source and compatible with ``GPL-3.0-or-later`` on **both**: