mirror of
https://github.com/ansible-collections/community.general.git
synced 2026-05-06 13:22:48 +00:00
Fixes more rST errors (#39042)
* removes include, avoids duplicate label rST warnings * reduces literal_block errors on playbooks_filters * addresses TOC errors * ref error on modules page * trying ref for list_of_database_modules
This commit is contained in:
@@ -108,5 +108,3 @@ The following topics will discuss how to develop and work with modules:
|
||||
`irc.freenode.net <http://irc.freenode.net>`_
|
||||
#ansible IRC chat channel
|
||||
|
||||
|
||||
.. include:: ./developing_module_utilities.rst
|
||||
|
||||
@@ -33,7 +33,7 @@ Although it's tempting to get straight into coding, there are a few things to be
|
||||
Naming Convention
|
||||
`````````````````
|
||||
|
||||
As you may have noticed when looking under ``lib/ansible/modules/`` we support up to two directories deep (but no deeper), e.g. `databases/mysql`. This is used to group files on disk as well as group related modules into categories and topics the Module Index, for example: :doc:`../list_of_database_modules`.
|
||||
As you may have noticed when looking under ``lib/ansible/modules/`` we support up to two directories deep (but no deeper), e.g. `databases/mysql`. This is used to group files on disk as well as group related modules into categories and topics the Module Index, for example: :ref:`list_of_database_modules`.
|
||||
|
||||
The directory name should represent the *product* or *OS* name, not the company name.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user