Fix TODO to avoid ezglossary warnings

Author: badlop

content/admin/configuration/basic.md

@@ -533,7 +533,7 @@ The following `ACLName` are pre-defined:
           "^yozhik$": "^example.(com|org)$"
     ```
 
-<!-- TODO: explain remaining parameters -->
+<!-- TODO:: explain remaining parameters -->
 
 - **`user_glob: Glob`**:
 

content/admin/install/source.md

@@ -201,7 +201,7 @@ Note that you probably need administrative privileges in the system to install e
 
 The created files and directories depend on the options provided to [`./configure`](#configure), by default they are:
 
-<!-- TODO: Check we are up to date -->
+<!-- TODO:: Check we are up to date -->
 
 - `/etc/ejabberd/`:  Configuration directory:
 

content/archive/old.md

@@ -1468,7 +1468,7 @@ following syntax:
          node_regexp:
            "^yozhik$": "^example.(com|org)$"
 ```
-<!-- TODO: explain remaining parameters -->
+<!-- TODO:: explain remaining parameters -->
 
 **`user_glob: Glob`**:
 
@@ -2863,7 +2863,7 @@ over BOSH.
 
 - **`use_cache: false|true`**:   Use this option and related ones as explained in section [Caching](#caching).
 
-<!-- TODO Document options:
+<!-- TODO:: Document options
 json, max_concat, max_inactivity, max_pause, prebind, ram_db_type,     queue_type, use_cache, cache_size, cache_missed, cache_life_time
 -->
 
@@ -3433,7 +3433,7 @@ Example DNS TXT configuration for Websocket:
 
 A test client can be found on Github: [Websocket test client](https://github.com/processone/xmpp-websocket-client)
 
-<!-- TODO We should probably embed a test Websocket client on the Websocket info get page. -->
+<!-- TODO:: We should probably embed a test Websocket client on the Websocket info get page. -->
 
 ## mod_jidprep
 

content/developer/ejabberd-api/commands.md

@@ -17,7 +17,7 @@ An ejabberd command is defined by an `#ejabberd_commands` Erlang record. The rec
 
     - `session`: For commands related to user XMPP sessions.
     - `roster`: Commands related to contact list management.
-    <!--  TODO: List other tags that we already use. -->
+    <!--  TODO:: List other tags that we already use. -->
 
 - **desc**: Description of the command for online help.
 - **module** and **function**: Module and function to call to execute the command logic.

content/developer/ejabberd-api/index.md

@@ -107,7 +107,7 @@ the following:
 - [Simple API configuration](simple-configuration.md)
 - Using ejabberd client API libraries and tools
 
-<!-- TODO: Using API with ejabberd command-line tool and Go based library -->
+<!-- TODO:: Using API with ejabberd command-line tool and Go based library -->
 
 The list of available commands is available in the [API Reference](admin-api.md) section.
 Additionally, you can check at runtime what commands are available in your installed server using [ejabberdctl](../../admin/guide/managing.md#ejabberdctl):

content/developer/ejabberd-api/oauth.md

@@ -172,13 +172,13 @@ Parameters are described in OAuth specification:
 - `token_type`: ejabberd supports `bearer` token type.
 - `expires_in`: This is the validity duration of the token, in seconds. When the token expires, a new authorization token will need to be generated an approved by the user.
 
-<!--- TODO: Does oauth2 allow token refresh ? Is it implemented or could
+<!--- TODO:: Does oauth2 allow token refresh ? Is it implemented or could
   it be implemented in ejabberd ? -->
 - `scope`: Confirms the granted scope to the requesting application. Several scopes can be passed, separated by '+'.
 - `state`: If a state parameter was passed by requesting application in authorization_token URL, it will be passed back to the
   application as a parameter of the `redirect_uri` to help with the client workflow.
 
-<!--- TODO: Add Android and iOS examples on how to get the token.  -->
+<!--- TODO:: Add Android and iOS examples on how to get the token.  -->
 
 ## Scopes
 
@@ -189,7 +189,7 @@ Parameters are described in OAuth specification:
   For example, there is a scope `registered_users`  because there is a command called [registered_users](admin-api.md#registered-users).
   Ensure you enable the module that defines the command that you want to use, see [Module configuration](#module-configuration) for details.
 
-<!--- TODO: As scope are generally provided by commands, which are
+<!--- TODO:: As scope are generally provided by commands, which are
 provided by enabled modules, we need to command to list enabled
 scopes.  We should also probably support scopes that are categories of
 commands (like user for example). Finally, we should probably allow

content/developer/ejabberd-api/simple-configuration.md

@@ -1,7 +1,7 @@
 # Simple ejabberd Rest API Configuration
 
 <!--
-TODO:
+TODO::
 
   - Link to page showing how to configure TLS on listeners
   - Link to page showing how to use Go ejabberd API client

content/livebooks/ejabberd-developer-livebook.md

@@ -1,7 +1,7 @@
 # The ejabberd Developer Livebook
 
 
-<!-- WARNING: Don't edit this file. This is generated from the *.livemd, please edit that one instead -->
+<!-- WARNING:: Don't edit this file. This is generated from the *.livemd, please edit that one instead -->
 
 !!! info
     This page is designed to run interactively using [Livebook](https://livebook.dev/).

content/livebooks/markdown_head.txt

@@ -1,5 +1,5 @@
 
-<!-- WARNING: Don't edit this file. This is generated from the *.livemd, please edit that one instead -->
+<!-- WARNING:: Don't edit this file. This is generated from the *.livemd, please edit that one instead -->
 
 !!! info
     This page is designed to run interactively using [Livebook](https://livebook.dev/).