Fix M(). (#591)

* Fix M().

* Break long line.

* Fix the remaining M(...).

* Break long line.

plugins/modules/database/mssql/mssql_db.py

@@ -51,7 +51,7 @@ options:
     default: 'no'
 notes:
    - Requires the pymssql Python package on the remote host. For Ubuntu, this
-     is as easy as pip install pymssql (See M(pip).)
+     is as easy as pip install pymssql (See M(ansible.builtin.pip).)
 requirements:
    - python >= 2.7
    - pymssql

plugins/modules/database/postgresql/postgresql_membership.py

@@ -16,8 +16,8 @@ description:
 - Users are roles with login privilege.
 - Groups are PostgreSQL roles usually without LOGIN privilege.
 - "Common use case:"
-- 1) add a new group (groups) by M(postgresql_user) module with I(role_attr_flags=NOLOGIN)
-- 2) grant them desired privileges by M(postgresql_privs) module
+- 1) add a new group (groups) by M(community.general.postgresql_user) module with I(role_attr_flags=NOLOGIN)
+- 2) grant them desired privileges by M(community.general.postgresql_privs) module
 - 3) add desired PostgreSQL users to the new group (groups) by this module
 options:
   groups:

plugins/modules/database/postgresql/postgresql_pg_hba.py

@@ -105,7 +105,7 @@ notes:
      This could give unexpected results with manual created hba files, if it was improperly sorted.
      For example a rule was created for a net first and for a ip in that net range next.
      In that situation, the 'ip specific rule' will never hit, it is in the C(pg_hba) file obsolete.
-     After the C(pg_hba) file is rewritten by the M(postgresql_pg_hba) module, the ip specific rule will be sorted above the range rule.
+     After the C(pg_hba) file is rewritten by the M(community.general.postgresql_pg_hba) module, the ip specific rule will be sorted above the range rule.
      And then it will hit, which will give unexpected results.
    - With the 'order' parameter you can control which field is used to sort first, next and last.
    - The module supports a check mode and a diff mode.

plugins/modules/database/postgresql/postgresql_query.py

@@ -15,7 +15,7 @@ short_description: Run PostgreSQL queries
 description:
 - Runs arbitrary PostgreSQL queries.
 - Can run queries from SQL script files.
-- Does not run against backup files. Use M(postgresql_db) with I(state=restore)
+- Does not run against backup files. Use M(community.general.postgresql_db) with I(state=restore)
   to run queries on files made by pg_dump/pg_dumpall utilities.
 options:
   query:

plugins/modules/database/postgresql/postgresql_set.py

@@ -21,7 +21,7 @@ description:
    - The module allows to reset parameter to boot_val (cluster initial value) by I(reset=yes) or remove parameter
      string from postgresql.auto.conf and reload I(value=default) (for settings with postmaster context restart is required).
    - After change you can see in the ansible output the previous and
-     the new parameter value and other information using returned values and M(debug) module.
+     the new parameter value and other information using returned values and M(ansible.builtin.debug) module.
 options:
   name:
     description:

plugins/modules/database/proxysql/proxysql_backend_servers.py

@@ -12,7 +12,7 @@ module: proxysql_backend_servers
 author: "Ben Mildren (@bmildren)"
 short_description: Adds or removes mysql hosts from proxysql admin interface.
 description:
-   - The M(proxysql_backend_servers) module adds or removes mysql hosts using
+   - The M(community.general.proxysql_backend_servers) module adds or removes mysql hosts using
      the proxysql admin interface.
 options:
   hostgroup_id:
@@ -96,8 +96,9 @@ EXAMPLES = '''
 # This example adds a server, it saves the mysql server config to disk, but
 # avoids loading the mysql server config to runtime (this might be because
 # several servers are being added and the user wants to push the config to
-# runtime in a single batch using the M(proxysql_manage_config) module).  It
-# uses supplied credentials to connect to the proxysql admin interface.
+# runtime in a single batch using the community.general.proxysql_manage_config
+# module).  It uses supplied credentials to connect to the proxysql admin
+# interface.
 
 - name: Add a server
   proxysql_backend_servers:

plugins/modules/database/proxysql/proxysql_global_variables.py

@@ -12,7 +12,7 @@ module: proxysql_global_variables
 author: "Ben Mildren (@bmildren)"
 short_description: Gets or sets the proxysql global variables.
 description:
-   - The M(proxysql_global_variables) module gets or sets the proxysql global
+   - The M(community.general.proxysql_global_variables) module gets or sets the proxysql global
      variables.
 options:
   variable:

plugins/modules/database/proxysql/proxysql_manage_config.py

@@ -13,7 +13,7 @@ module: proxysql_manage_config
 author: "Ben Mildren (@bmildren)"
 short_description: Writes the proxysql configuration settings between layers.
 description:
-   - The M(proxysql_global_variables) module writes the proxysql configuration
+   - The M(community.general.proxysql_global_variables) module writes the proxysql configuration
      settings between layers. Currently this module will always report a
      changed state, so should typically be used with WHEN however this will
      change in a future version when the CHECKSUM table commands are available

plugins/modules/database/proxysql/proxysql_mysql_users.py

@@ -12,7 +12,7 @@ module: proxysql_mysql_users
 author: "Ben Mildren (@bmildren)"
 short_description: Adds or removes mysql users from proxysql admin interface.
 description:
-   - The M(proxysql_mysql_users) module adds or removes mysql users using the
+   - The M(community.general.proxysql_mysql_users) module adds or removes mysql users using the
      proxysql admin interface.
 options:
   username:
@@ -91,8 +91,9 @@ EXAMPLES = '''
 # This example adds a user, it saves the mysql user config to disk, but
 # avoids loading the mysql user config to runtime (this might be because
 # several users are being added and the user wants to push the config to
-# runtime in a single batch using the M(proxysql_manage_config) module).  It
-# uses supplied credentials to connect to the proxysql admin interface.
+# runtime in a single batch using the community.general.proxysql_manage_config
+# module).  It uses supplied credentials to connect to the proxysql admin
+# interface.
 
 - name: Add a user
   proxysql_mysql_users:

plugins/modules/database/proxysql/proxysql_query_rules.py

@@ -12,7 +12,7 @@ module: proxysql_query_rules
 author: "Ben Mildren (@bmildren)"
 short_description: Modifies query rules using the proxysql admin interface.
 description:
-   - The M(proxysql_query_rules) module modifies query rules using the
+   - The M(community.general.proxysql_query_rules) module modifies query rules using the
      proxysql admin interface.
 options:
   rule_id:
@@ -79,7 +79,7 @@ options:
     description:
       - Route matched queries to this hostgroup. This happens unless there is a
         started transaction and the logged in user has
-        I(transaction_persistent) set to C(True) (see M(proxysql_mysql_users)).
+        I(transaction_persistent) set to C(True) (see M(community.general.proxysql_mysql_users)).
   cache_ttl:
     description:
       - The number of milliseconds for which to cache the result of the query.
@@ -150,8 +150,8 @@ EXAMPLES = '''
 # hostgroup, it saves the mysql query rule config to disk, but avoids loading
 # the mysql query config config to runtime (this might be because several
 # rules are being added and the user wants to push the config to runtime in a
-# single batch using the M(proxysql_manage_config) module). It uses supplied
-# credentials to connect to the proxysql admin interface.
+# single batch using the community.general.proxysql_manage_config module). It
+# uses supplied credentials to connect to the proxysql admin interface.
 
 - name: Add a rule
   proxysql_query_rules:

plugins/modules/database/proxysql/proxysql_replication_hostgroups.py

@@ -48,8 +48,8 @@ EXAMPLES = '''
 # to disk, but avoids loading the mysql server config to runtime (this might be
 # because several replication hostgroup are being added and the user wants to
 # push the config to runtime in a single batch using the
-# M(proxysql_manage_config) module).  It uses supplied credentials to connect
-# to the proxysql admin interface.
+# community.general.proxysql_manage_config module).  It uses supplied credentials
+# to connect to the proxysql admin interface.
 
 - name: Add a replication hostgroup
   proxysql_replication_hostgroups:

plugins/modules/database/proxysql/proxysql_scheduler.py

@@ -12,7 +12,7 @@ module: proxysql_scheduler
 author: "Ben Mildren (@bmildren)"
 short_description: Adds or removes schedules from proxysql admin interface.
 description:
-   - The M(proxysql_scheduler) module adds or removes schedules using the
+   - The M(community.general.proxysql_scheduler) module adds or removes schedules using the
      proxysql admin interface.
 options:
   active:
@@ -72,8 +72,9 @@ EXAMPLES = '''
 # This example adds a schedule, it saves the scheduler config to disk, but
 # avoids loading the scheduler config to runtime (this might be because
 # several servers are being added and the user wants to push the config to
-# runtime in a single batch using the M(proxysql_manage_config) module).  It
-# uses supplied credentials to connect to the proxysql admin interface.
+# runtime in a single batch using the community.general.proxysql_manage_config
+# module).  It uses supplied credentials to connect to the proxysql admin
+# interface.
 
 - name: Add a schedule
   proxysql_scheduler:

plugins/modules/database/vertica/vertica_info.py

@@ -15,7 +15,7 @@ short_description: Gathers Vertica database facts.
 description:
   - Gathers Vertica database information.
   - This module was called C(vertica_facts) before Ansible 2.9, returning C(ansible_facts).
-    Note that the M(vertica_info) module no longer returns C(ansible_facts)!
+    Note that the M(community.general.vertica_info) module no longer returns C(ansible_facts)!
 options:
   cluster:
     description: