atomic fix - further attempt at making the docs style match existing content

Author: shadowguardian507-irl

docs/source/userguide/commands.rst

@@ -194,16 +194,17 @@ More info on the general OVMS MQTT topic scheme can be found
 TLS client certificate commands
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-For MQTT brokers requiring client certificate authentication (mTLS), use::
+If the broker needs a client certificate (mTLS)::
 
   OVMS# server v3 tlsclient import <cert_path> <key_path>
   OVMS# server v3 tlsclient status
+  OVMS# server v3 tlsclient info
   OVMS# server v3 tlsclient check
   OVMS# server v3 tlsclient reload
   OVMS# server v3 tlsclient clear
 
-Certificate and key files are stored under ``/store/tls/``. Use ``import`` to load PEM files,
-``check`` to validate the pair, and ``reload`` to apply changes to the active connection.
+Files are stored under ``/store/tls/``. Use ``check`` to validate the cert/key pair,
+``reload`` to reconnect and apply changes.
 
 
 ------------------

docs/source/userguide/components.rst

@@ -123,13 +123,13 @@ Send all ``v.b`` metrics except ``v.b.soc``::
   OVMS# config set server.v3 metrics.include v.b.*
   OVMS# config set server.v3 metrics.exclude v.b.soc
 
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 Broker compatibility options
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-Some MQTT brokers impose limits that require additional configuration:
+Some brokers have additional requirements:
 
-- ``retain.depth.limit`` (default: ``no``) — omits the RETAIN flag on topics deeper than 8 path segments. Required for AWS IoT Core.
+- ``retain.depth.limit`` (default: ``no``) — omits the RETAIN flag on topics deeper than 8 path segments. Needed for AWS IoT Core, which silently drops retained publishes on topics deeper than 8 levels.
 
 Example::
 
@@ -142,12 +142,12 @@ Example::
 
 These options can also be set from the **Config → Server V3 (MQTT)** web page.
 
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^
 TLS client authentication
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+^^^^^^^^^^^^^^^^^^^^^^^^^
 
-MQTT brokers that require client certificate authentication (mTLS) are supported.
-Paste PEM-encoded certificate and key into the **Config → Server V3 (MQTT)** web page,
+The module supports client certificate authentication (mTLS) for brokers that need it.
+Paste the PEM certificate and key into the **Config → Server V3 (MQTT)** web page,
 or use the CLI::
 
   OVMS# server v3 tlsclient import /sd/client.crt /sd/client.key