From 8a46ff8963d18d61a46a536976d3aeb31e9d0dba Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Rom=C3=A1n=20C=C3=A1rdenas?= Date: Fri, 4 Jan 2019 18:31:42 +0100 Subject: [PATCH] minor changes --- docs/references/broker.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/references/broker.rst b/docs/references/broker.rst index 377ca87..f66c7d9 100644 --- a/docs/references/broker.rst +++ b/docs/references/broker.rst @@ -105,9 +105,9 @@ The ``topic-check`` section setup access control policies for publishing and sub * ``enabled``: set to true if you want to impose an access control policy. Otherwise, set it to false. * ``plugins``: defines the list of activated plugins. Note the plugins must be defined in the ``hbmqtt.broker.plugins`` `entry point `_. * aditional parameters: depending on the plugin used for access control, additional parameters should be added. - * In case of ``topic_acl`` plugin, the Access Control List (ACL) must be defined in the parameter ``acl``. - * For each of the usernames, a list with the allowed topics must be defined. - * If the client logs in anonymously, the ``anonymous`` entry within the ACL is used in order to grant/deny subscriptions. +** In case of ``topic_acl`` plugin, the Access Control List (ACL) must be defined in the parameter ``acl``. +*** For each of the usernames, a list with the allowed topics must be defined. +*** If the client logs in anonymously, the ``anonymous`` entry within the ACL is used in order to grant/deny subscriptions. .. [1] See `PyYAML `_ for loading YAML files as Python dict.