Add more glossary definitions, use some of them, improve some markdown

Author: badlop

content/admin/guide/managing.md

@@ -2,14 +2,21 @@
 
 ## ejabberdctl
 
-With the `ejabberdctl` command line administration script you can
-execute `ejabberdctl commands` (described in the next section,
-[ejabberdctl Commands](#ejabberdctl-commands)) and also many general
-`ejabberd commands` (described in section
-[ejabberd Commands](#ejabberd-commands)).
-This means you can start, stop and perform many
-other administrative tasks in a local or remote ejabberd server (by
-providing the argument `–node NODENAME`).
+def:ejabberdctl
+: Command line administration script to start/stop ejabberd and execute API commands.
+
+With `ejabberdctl` you can execute:
+
+- [ejabberdctl commands](#ejabberdctl-commands)
+  like `start` and `stop` an ejabberd server
+
+- [ejabberd API commands](#ejabberd-commands)
+  for everyday administrative tasks in your running ejabberd servers
+
+`ejabberdctl` can connect to a local ejabberd server,
+and even remote ones if you properly set the
+[erlang cookie](security.md#erlang-cookie)
+and provide the argument `–node NODENAME`.
 
 The `ejabberdctl` script can be configured in the file
 `ejabberdctl.cfg`. This file includes detailed information about each

content/admin/guide/mqtt/index.md

@@ -27,10 +27,10 @@ In summary:
 - You get support on solution design for real-time infrastructure and can get help choosing between XMPP and MQTT, from
 a vendor that has no interest in selling one protocol more than another.
 
-ejabberd Business Edition offers a different clustering than eCS. Using MQTT with ejabberd Business Edition means
+ejabberd Business Edition offers a different clustering than [](def:eCS). Using MQTT with ejabberd Business Edition means
 you can leverage:
 
-- The clustering engine of eBE will be used for the MQTT service. It means that you have a more scalable cluster, that supports
+- The clustering engine of [](def:eBE) will be used for the MQTT service. It means that you have a more scalable cluster, that supports
 geoclustering. With geoclustering, you can deploy a single MQTT service across different datacenters, spread in different
 regions. You can deploy a truly global service.
 - The backend integration that are supported in ejabberd Business Edition will be available in MQTT. You have no need

content/admin/introduction.md

@@ -4,7 +4,7 @@
 
 **ejabberd** is *cross-platform*, distributed, fault-tolerant, and based on open standards to achieve real-time communication.
 
-**ejabberd** is designed to be a *rock-solid and feature rich* XMPP server.
+**ejabberd** is designed to be a *rock-solid and feature rich* [](def:XMPP) server.
 
 **ejabberd** is suitable for small deployments, whether they need to be *scalable* or not, as well as extremely large deployments.
 

content/developer/ejabberd-api/index.md

@@ -17,7 +17,7 @@ how to start using ejabberd's API,
 how to adjust it to your needs,
 and integrate ejabberd with your existing systems.
 
-def:API command
+def:api command
 : Command defined in some ejabberd module API backend, that can be executed using some API frontend.
 
 ejabberd's API currently includes over 200 API Commands,

content/get-started/index.md

@@ -2,7 +2,7 @@
 
 ## Meet **ejabberd**, your superpowerful messaging framework
 
-This web site is dedicated to help you use and develop for ejabberd XMPP messaging server.
+This web site is dedicated to help you use and develop for ejabberd [](def:XMPP) messaging server.
 
 ejabberd has been in development since 2002 and is used all over the world to power the largest XMPP deployments.
 This project is so versatile that you can deploy it and customize it for very large scale, no matter what your use case is.
@@ -33,16 +33,21 @@ Welcome to the beginning of your journey of ejabberd mastery!
 
 ## Options to use ejabberd
 
-ejabberd can be used in different ways. The most common one is to use ejabberd Community Edition. This is the standard Open Source version that everyone loves: highly scalable and flexible.
+ejabberd can be used in different ways. The most common one is:
+
+- [**ejabberd Community Server**](https://www.process-one.net/ejabberd/),
+  the public Open Source version
+  that everyone loves: highly scalable and flexible.
 
 Fortunately, if you need more than just the ejabberd platform software, [ProcessOne](https://www.process-one.net/) can help you with a commercial offering. Commercial offering come in two type of packaging:
 
-- **ejabberd Business Edition**, including features for large companies
+- [**ejabberd Business Edition**](https://www.process-one.net/ejabberd-features/)
+  including features for large companies
   (enhanced geodistributed companies and mobile support to develop
   own, rich clients) and world-class support, that can please even the
   most demanding businesses, with 24/7 options.
 
-- [Fluux.io](https://fluux.io) being a way to access and benefit of all the features
+- [**Fluux.io**](https://fluux.io) being a way to access and benefit of all the features
   of ejabberd Business Edition at an attractive and scalable
   price. Fluux.io allows you to keep control of your data thanks
   to integration API you can implement on your backend to become a

content/glossary.md

@@ -4,16 +4,72 @@
 
 ---
 
+def:bosh
+: [Bidirectional-streams Over Synchronous HTTP](https://xmpp.org/about/technology-overview/#bosh): an extension for [XMPP](def:XMPP) defined in [XEP-0124](https://xmpp.org/extensions/xep-0124.html) that allows long lived connections for XMPP over HTTP.
+  See [mod_bosh](admin/configuration/modules.md#mod_bosh).
+
 def:command
 : May refer to:
 
     - [](def:ad-hoc command)
     - [](def:API command)
     - shell command
 
+def:eBE
+: ejabberd Business Edition.
+  See [Options to use ejabberd](get-started/index.md#options-to-use-ejabberd)
+
+def:eCS
+: ejabberd Community Server, see [Options to use ejabberd](get-started/index.md#options-to-use-ejabberd)
+
+def:erlang
+: [Erlang](https://www.erlang.org/) is a programming language used to build massively scalable soft real-time systems with requirements on high availability. Some of its uses are in telecoms, banking, e-commerce, computer telephony and instant messaging. Erlang's runtime system has built-in support for concurrency, distribution and fault tolerance.
+
+def:iq
+: [Stanza](def:Stanza) that provides a structured request-response mechanism.
+
+def:jid
+: [Jabber ID](https://xmpp.org/rfcs/rfc6122.html) is a unique identifier for an entity in the XMPP network (like a server, a service, an account, a chat room, ...). It consists of three parts: a local part, a domain part, and an optional resource part, formatted as `localpart@domain/resource`.
+
+def:mnesia
+: [Mnesia](https://www.erlang.org/doc/apps/mnesia/mnesia_chap1.html) is a distributed database specifically designed for industrial-grade telecommunications applications written in Erlang. It is used by default in ejabberd as it requires no initial configuration. However, for large volumes of data, it is recommended to [setup a SQL database](admin/configuration/database.md).
+
+def:muc
+: [Multi-User Chat](https://xmpp.org/about/technology-overview/#muc), an extension for [XMPP](def:XMPP) defined in [XEP-0045](https://xmpp.org/extensions/xep-0045.html) for multi-party information exchange whereby multiple users can exchange messages in the context of a chat room.
+  See [mod_muc](admin/configuration/modules.md#mod_muc).
+
 def:node
 : May refer to:
 
     - disco node, see [mod_disco](admin/configuration/modules.md#mod_disco)
     - [](def:erlang node)
     - pubsub node, see [mod_pubsub](admin/configuration/modules.md#mod_pubsub)
+
+def:omemo
+: OMEMO is an extension for [XMPP](def:XMPP) defined in [XEP-0384](https://xmpp.org/extensions/xep-0384.html) that allows end-to-end encryption between clients.
+
+def:otp
+: [Open Telecom Platform](https://www.erlang.org/) is a set of Erlang libraries and design principles providing middle-ware to develop these systems. It includes its own distributed database, applications to interface towards other languages, debugging and release handling tools.
+
+def:presence
+: [Stanza](def:Stanza) that provides information about network availability of an account (online, away, offline, ...).
+
+def:pubsub
+: [Publish-Subscribe](https://xmpp.org/about/technology-overview/#pubsub), an extension for [XMPP](def:XMPP) defined in [XEP-0060](https://xmpp.org/extensions/xep-0060.html) for  for generic publish-subscribe functionality.
+  See [mod_pubsub](admin/configuration/modules.md#mod_pubsub).
+
+def:roster
+: A list of contacts of an account, which is stored on the server, used to manage [presence](def:presence).
+
+def:stanza
+: [XMPP](def:XMPP) packet of type `message`, `presence` or [IQ](def:IQ).
+
+def:vCard
+: Virtual Card, an extension for [XMPP](def:XMPP) defined in [XEP-0054](https://xmpp.org/extensions/xep-0054.html) that allows to publish contact information like name, email, phone number, address, etc.
+  See [mod_vcard](admin/configuration/modules.md#mod_vcard).
+
+def:vhost
+: Virtual Host, a domain name served by ejabberd that corresponds to a [XMPP Domain](admin/configuration/basic.md#xmpp-domains).
+
+def:xmpp
+: [Extensible Messaging and Presence Protocol](https://xmpp.org/about/technology-overview/): an open protocol based in XML for real-time communications.