Fix markdown typos and update links

Author: badlop

content/admin/configuration/listen-options.md

@@ -191,7 +191,7 @@ This option specifies the maximum number of elements in the queue of
         [`ejabberd_service`](listen.md#ejabberd_service)
         and [`ejabberd_c2s`](listen.md#ejabberd_c2s)
         listeners, or also globally for
-        [`ejabberd_s2s_out`](listen.md#ejabberd_s2s_out).
+        `ejabberd_s2s_out`.
         If the option is not specified for
  `ejabberd_service` or `ejabberd_c2s` listeners, the globally
  configured value is used. The allowed values are integers and

content/admin/configuration/listen.md

@@ -57,7 +57,7 @@ General listen options supported:
 [starttls](listen-options.md#starttls),
 [starttls_required](listen-options.md#starttls_required),
 [tls](listen-options.md#tls),
-[tls_compression](listen-options.md#tls-compression),
+[tls_compression](listen-options.md#tls_compression),
 [tls_verify](listen-options.md#tls_verify),
 [zlib](listen-options.md#zlib).
 
@@ -79,7 +79,7 @@ General listen options supported:
 [send_timeout](listen-options.md#send_timeout),
 [shaper](listen-options.md#shaper),
 [tls](listen-options.md#tls),
-[tls_compression](listen-options.md#tls-compression).
+[tls_compression](listen-options.md#tls_compression).
 
 ## ejabberd_service
 
@@ -101,9 +101,9 @@ General listen options supported:
 [protocol_options](listen-options.md#protocol_options),
 [send_timeout](listen-options.md#send_timeout),
 [shaper](listen-options.md#shaper),
-[shaper_rule](listen-options.md#shaper-rule),
+[shaper_rule](listen-options.md#shaper_rule),
 [tls](listen-options.md#tls),
-[tls_compression](listen-options.md#tls-compression).
+[tls_compression](listen-options.md#tls_compression).
 
 ## mod_mqtt
 
@@ -352,7 +352,7 @@ Options:
 [send_timeout](listen-options.md#send_timeout),
 [tag](listen-options.md#tag),
 [tls](listen-options.md#tls),
-[tls_compression](listen-options.md#tls-compression),
+[tls_compression](listen-options.md#tls_compression),
 and the [trusted_proxies](toplevel.md#trusted_proxies) top-level option.
 
 ### ejabberd_http_ws
@@ -403,7 +403,7 @@ ejabberd [21.12](../../archive/21.12/index.md) release notes.
 ### ejabberd_xmlrpc
 
 Handles XML-RPC requests to execute
-[ejabberd commands](../guide/managing.md#ejabberd_commands).
+[API commands](../../developer/ejabberd-api/admin-api.md).
 It is configured as a request handler in
 [ejabberd_http](#ejabberd_http).
 

content/admin/guide/managing.md

@@ -70,8 +70,8 @@ available parameters are:
 
 If there is an ejabberd server running in the system, `ejabberdctl`
 shows the `ejabberdctl commands` described below and all the
-`ejabberd commands` available in that server (see
-[List of ejabberd Commands](./managing.md#list-of-ejabberd-commands)).
+`API commands` available in that server (see the
+[full list of API Commands](../../developer/ejabberd-api/admin-api.md)).
 
 The `ejabberdctl commands` are:
 
@@ -425,14 +425,14 @@ NEWFILE=/tmp/new.backup
     ```
 
 6. Convert the backup to new node name using
-    [mnesia_change_nodename](../../developer/ejabberd-api/admin-api.md/#mnesia-change-nodename):
+    [mnesia_change_nodename](../../developer/ejabberd-api/admin-api.md/#mnesia_change_nodename):
 
     ``` sh
     ejabberdctl mnesia_change_nodename $OLDNODE $NEWNODE $OLDFILE $NEWFILE
     ```
 
 7. Install the backup file as a fallback using
-    [install_fallback](../../developer/ejabberd-api/admin-api.md#install-fallback):
+    [install_fallback](../../developer/ejabberd-api/admin-api.md#install_fallback):
 
     ``` sh
     ejabberdctl install_fallback $NEWFILE

content/archive/20.04/index.md

@@ -4,7 +4,7 @@ This section contains some archived sections for ejabberd 20.04.
 
 If you are upgrading ejabberd from a previous release, you can check:
 
-* [Specific version upgrade notes](../../admin/upgrade/index.md#specific_version_upgrade_notes)
+* [Specific version upgrade notes](../../admin/upgrade/index.md#specific-version-upgrade-notes)
 * [ejabberd 20.04 release announcement](https://www.process-one.net/blog/ejabberd-20-04/)
 * [Docs Github Compare from 20.03](https://github.com/processone/docs.ejabberd.im/compare/20.03..20.04)
 * [ejabberd Github Compare from 20.03](https://github.com/processone/ejabberd/compare/20.03..20.04)

content/archive/20.04/listen-options.md

@@ -127,7 +127,7 @@ This option specifies the maximum number of elements in the queue of
         [`ejabberd_service`](listen.md#ejabberd_service)
         and [`ejabberd_c2s`](listen.md#ejabberd_c2s)
         listeners, or also globally for
-        [`ejabberd_s2s_out`](listen.md#ejabberd_s2s-out).
+        `ejabberd_s2s_out`.
         If the option is not specified for
  `ejabberd_service` or `ejabberd_c2s` listeners, the globally
  configured value is used. The allowed values are integers and

content/archive/20.04/listen.md

@@ -81,7 +81,7 @@ Options:
 [starttls](listen-options.md#starttls),
 [starttls_required](listen-options.md#starttls_required),
 [tls](listen-options.md#tls),
-[tls_compression](listen-options.md#tls-compression),
+[tls_compression](listen-options.md#tls_compression),
 [tls_verify](listen-options.md#tls_verify),
 [zlib](listen-options.md#zlib).
 
@@ -98,7 +98,7 @@ Options:
 [protocol_options](listen-options.md#protocol_options),
 [shaper](listen-options.md#shaper),
 [tls](listen-options.md#tls),
-[tls_compression](listen-options.md#tls-compression).
+[tls_compression](listen-options.md#tls_compression).
 
 ### ejabberd_service
 
@@ -121,9 +121,9 @@ Options:
 [password](listen-options.md#password),
 [protocol_options](listen-options.md#protocol_options),
 [shaper](listen-options.md#shaper),
-[shaper_rule](listen-options.md#shaper-rule),
+[shaper_rule](listen-options.md#shaper_rule),
 [tls](listen-options.md#tls),
-[tls_compression](listen-options.md#tls-compression).
+[tls_compression](listen-options.md#tls_compression).
 
 ### ejabberd_sip
 
@@ -173,7 +173,7 @@ With the proper request handlers configured, this serves HTTP services like
 [Fileserver](modules.md#mod_http_fileserver),
 [OAuth](../../developer/ejabberd-api/oauth.md),
 [Upload](modules.md#mod_http_upload),
-[WebAdmin](../../admin/guide/managing.md#web_admin),
+[WebAdmin](../../admin/guide/managing.md#web-admin),
 [WebSocket](listen.md#ejabberd_http_ws),
 [XMP-RPC](listen.md#ejabberd_xmlrpc).
 
@@ -186,7 +186,7 @@ Options:
 [request_handlers](listen-options.md#request_handlers),
 [tag](listen-options.md#tag),
 [tls](listen-options.md#tls),
-[tls_compression](listen-options.md#tls-compression),
+[tls_compression](listen-options.md#tls_compression),
 and the [trusted_proxies](toplevel.md#trusted_proxies) top-level option.
 
 ### mod_mqtt
@@ -429,7 +429,7 @@ A test client can be found on Github: [Websocket test client](https://github.com
 ## ejabberd_xmlrpc
 
 Handles XML-RPC requests to execute
-[ejabberd commands](../../admin/guide/managing.md#ejabberd_commands).
+[API commands](../../developer/ejabberd-api/admin-api.md).
 It is configured as a request handler in
 [ejabberd_http](listen.md#ejabberd_http).
 
@@ -502,7 +502,7 @@ It's possible to use OAuth for authentication instead of plain password, see
 
 In ejabberd 20.03 and older, it was possible to configure `ejabberd_xmlrpc` as a
 listener, see the old document for reference and example configuration:
-[Listening Module](../old.md#listening_module).
+[Listening Ports](../old.md#listening-ports).
 
 Just for reference, there's also the old
 [`ejabberd_xmlrpc documentation`](https://ejabberd.im/ejabberd_xmlrpc).
@@ -529,7 +529,7 @@ For example, the following simple configuration defines:
  service.
 
 - Port 5281 listens for HTTP requests, using HTTPS to serve HTTP-Bind
- (BOSH) and the Web Admin as explained in [Managing: Web Admin](../../admin/guide/managing.md#web_admin). The
+ (BOSH) and the Web Admin as explained in [Managing: Web Admin](../../admin/guide/managing.md#web-admin). The
  socket only listens connections to the IP address 127.0.0.1.
 
 ``` yaml
@@ -603,7 +603,7 @@ In this example, the following configuration defines that:
 
 - Port 5280 is serving the Web Admin and the HTTP-Bind (BOSH) service in
  all the IPv4 addresses. Note that it is also possible to serve them
- on different ports. The second example in section [Managing: Web Admin](../../admin/guide/managing.md#web_admin) shows
+ on different ports. The second example in section [Managing: Web Admin](../../admin/guide/managing.md#web-admin) shows
  how exactly this can be done. A request handler to serve MQTT over Websocket is also defined.
 
 - All users except for the administrators have a traffic of limit

content/archive/20.04/modules.md

@@ -2753,11 +2753,11 @@ password in multiple places.
 - Connection parameters: The module also accepts the connection
     parameters, all of which default to the top-level parameter of the
     same name, if unspecified. See [LDAP
-    Connection](../../admin/configuration/ldap.md#ldap_connection) section for
+    Connection](../../admin/configuration/ldap.md#ldap-connection) section for
     more information about them.
 
 Check also the [Configuration
-examples](../../admin/configuration/ldap.md#configuration_examples) section to
+examples](../../admin/configuration/ldap.md#configuration-examples) section to
 get details about retrieving the roster, and configuration examples
 including Flat DIT and Deep DIT.
 
@@ -2834,7 +2834,7 @@ section Filters.
 - __ldap\_memberattr\_format\_re__  
 A regex for extracting user ID from the value of the attribute named by
 *ldap\_memberattr*. Check the LDAP [Control
-Parameters](../../admin/configuration/ldap.md#control_parameters) section.
+Parameters](../../admin/configuration/ldap.md#control-parameters) section.
 
 - __ldap\_password__  
 Same as top-level *ldap\_password* option, but applied to this module

content/archive/20.07/index.md

@@ -4,7 +4,7 @@ This section contains some archived sections for ejabberd 20.07.
 
 If you are upgrading ejabberd from a previous release, you can check:
 
-* [Specific version upgrade notes](../../admin/upgrade/index.md#specific_version_upgrade_notes)
+* [Specific version upgrade notes](../../admin/upgrade/index.md#specific-version-upgrade-notes)
 * [ejabberd 20.07 release announcement](https://www.process-one.net/blog/ejabberd-20-07/)
 * [Docs Github Compare from 20.04](https://github.com/processone/docs.ejabberd.im/compare/20.04..20.07)
 * [ejabberd Github Compare from 20.04](https://github.com/processone/ejabberd/compare/20.04..20.07)

content/archive/20.07/listen-options.md

@@ -127,7 +127,7 @@ This option specifies the maximum number of elements in the queue of
         [`ejabberd_service`](listen.md#ejabberd_service)
         and [`ejabberd_c2s`](listen.md#ejabberd_c2s)
         listeners, or also globally for
-        [`ejabberd_s2s_out`](listen.md#ejabberd_s2s-out).
+        `ejabberd_s2s_out`.
         If the option is not specified for
  `ejabberd_service` or `ejabberd_c2s` listeners, the globally
  configured value is used. The allowed values are integers and

content/archive/20.07/listen.md

@@ -83,7 +83,7 @@ Options:
 [starttls](listen-options.md#starttls),
 [starttls_required](listen-options.md#starttls_required),
 [tls](listen-options.md#tls),
-[tls_compression](listen-options.md#tls-compression),
+[tls_compression](listen-options.md#tls_compression),
 [tls_verify](listen-options.md#tls_verify),
 [zlib](listen-options.md#zlib).
 
@@ -100,7 +100,7 @@ Options:
 [protocol_options](listen-options.md#protocol_options),
 [shaper](listen-options.md#shaper),
 [tls](listen-options.md#tls),
-[tls_compression](listen-options.md#tls-compression).
+[tls_compression](listen-options.md#tls_compression).
 
 ## ejabberd_service
 
@@ -123,9 +123,9 @@ Options:
 [password](listen-options.md#password),
 [protocol_options](listen-options.md#protocol_options),
 [shaper](listen-options.md#shaper),
-[shaper_rule](listen-options.md#shaper-rule),
+[shaper_rule](listen-options.md#shaper_rule),
 [tls](listen-options.md#tls),
-[tls_compression](listen-options.md#tls-compression).
+[tls_compression](listen-options.md#tls_compression).
 
 ## ejabberd_sip
 
@@ -175,7 +175,7 @@ With the proper request handlers configured, this serves HTTP services like
 [Fileserver](modules.md#mod_http_fileserver),
 [OAuth](../../developer/ejabberd-api/oauth.md),
 [Upload](modules.md#mod_http_upload),
-[WebAdmin](../../admin/guide/managing.md#web_admin),
+[WebAdmin](../../admin/guide/managing.md#web-admin),
 [WebSocket](listen.md#ejabberd_http_ws),
 [XMP-RPC](listen.md#ejabberd_xmlrpc).
 
@@ -188,7 +188,7 @@ Options:
 [request_handlers](listen-options.md#request_handlers),
 [tag](listen-options.md#tag),
 [tls](listen-options.md#tls),
-[tls_compression](listen-options.md#tls-compression),
+[tls_compression](listen-options.md#tls_compression),
 and the [trusted_proxies](toplevel.md#trusted_proxies) top-level option.
 
 ## mod_mqtt
@@ -435,7 +435,7 @@ A test client can be found on Github: [Websocket test client](https://github.com
 # ejabberd_xmlrpc
 
 Handles XML-RPC requests to execute
-[ejabberd commands](../../admin/guide/managing.md#ejabberd_commands).
+[API commands](../../developer/ejabberd-api/admin-api.md).
 It is configured as a request handler in
 [ejabberd_http](listen.md#ejabberd_http).
 
@@ -508,7 +508,7 @@ It's possible to use OAuth for authentication instead of plain password, see
 
 In ejabberd 20.03 and older, it was possible to configure `ejabberd_xmlrpc` as a
 listener, see the old document for reference and example configuration:
-[Listening Module](../old.md#listening_module).
+[Listening Ports](../old.md#listening-ports).
 
 Just for reference, there's also the old
 [`ejabberd_xmlrpc documentation`](http://www.ejabberd.im/ejabberd_xmlrpc).
@@ -535,7 +535,7 @@ For example, the following simple configuration defines:
  service.
 
 - Port 5281 listens for HTTP requests, using HTTPS to serve HTTP-Bind
- (BOSH) and the Web Admin as explained in [Managing: Web Admin](../../admin/guide/managing.md#web_admin). The
+ (BOSH) and the Web Admin as explained in [Managing: Web Admin](../../admin/guide/managing.md#web-admin). The
  socket only listens connections to the IP address 127.0.0.1.
 
 ``` yaml
@@ -609,7 +609,7 @@ In this example, the following configuration defines that:
 
 - Port 5280 is serving the Web Admin and the HTTP-Bind (BOSH) service in
  all the IPv4 addresses. Note that it is also possible to serve them
- on different ports. The second example in section [Managing: Web Admin](../../admin/guide/managing.md#web_admin) shows
+ on different ports. The second example in section [Managing: Web Admin](../../admin/guide/managing.md#web-admin) shows
  how exactly this can be done. A request handler to serve MQTT over Websocket is also defined.
 
 - All users except for the administrators have a traffic of limit