--- a/doc/libervia-cli/encryption.rst	Fri Jun 11 09:19:43 2021 +0200
+++ b/doc/libervia-cli/encryption.rst	Fri Jun 11 09:21:41 2021 +0200
@@ -3,7 +3,7 @@
 ========================================
 
 Libervia being an XMPP client does encryption by default between client and server. In
-addition, SàT is also capable of doing end-to-end (e2e) encryption, meaning that the
+addition, Libervia is also capable of doing end-to-end (e2e) encryption, meaning that the
 payload of messages are encrypted to be hidden from the servers (and their
 administrators).  The ``encryption`` commands are here to handle those e2e encryption
 sessions and algorithms.
@@ -56,7 +56,7 @@
 You need to specify the JID of the entity you want to start a session with as a positional
 argument.
 
-By default, SàT will select itself the algorithm to use among those available, but you can
+By default, Libervia will select itself the algorithm to use among those available, but you can
 specify one using either its name with ``-n NAME, --name NAME`` or its namespace using
 ``-N NAMESPACE, --namespace``. ``NAME`` is the short name of the algorithm, e.g. ``omemo``
 while the namespace is the longer (e.g. ``urn:xmpp:otr:0``).
@@ -72,7 +72,7 @@
 examples
 --------
 
-Start e2e encryption with Pierre, using the algorithm selected by SàT::
+Start e2e encryption with Pierre, using the algorithm selected by Libervia::
 
   $ li encryption start louise@example.net
 
@@ -87,7 +87,7 @@
 argument.
 
 After this command is run, the messages with specified entity will not be e2e encrypted
-anymore (but this won't affect encryption between SàT and XMPP server and between XMPP
+anymore (but this won't affect encryption between Libervia and XMPP server and between XMPP
 servers).
 
 example