doc (jp): typos (thanks tbart)

This commit is contained in:
Goffi 2019-10-11 16:15:09 +02:00
commit 1f5a0f49f1
2 changed files with 4 additions and 4 deletions

View file

@ -67,7 +67,7 @@ can change this behaviour by using ``--encrypt-noreplace``: in this case the com
fail in case of conflict (e2e encryption is requested with a new algorithm while an e2e
encryption session was already started with an other algorithm), and return a non-zero
code. If an e2e encryption session was already started with the requested algorithm, the
command will succeed in all cases an nothing will be changed.
command will succeed in all cases and nothing will be changed.
examples
--------
@ -101,13 +101,13 @@ trust ui
========
Run the user interface to handle trust with given entity and given algorithm. The user
interface depends of the algorithm used, but it generally shows you the fingerprints
interface depends on the algorithm used, but it generally shows you the fingerprints
associated with your contact or contact devices, and asks you if you trust them or not.
The only mandatory argument is the jid of your contact.
By default the currently active encryption session algorithm is used, but you may manage
trust for an other algorithm by using ``-n NAME, --name NAME`` or ``-N NAMESPACE,
trust for another algorithm by using ``-n NAME, --name NAME`` or ``-N NAMESPACE,
--namespace NAMESPACE``.
.. note::

View file

@ -25,7 +25,7 @@ which can be used on any command, so if you need help on ``message send`` comman
With jp, you always enter commands first, then options and arguments.
There are several levels of commands: first one is the main categorie (``message``,
There are several levels of commands: first one is the main category (``message``,
``blog``, ``avatar``, etc.), then there are often subcommands (e.g. ``message send``).
After the commands come the options. For instance if you want to send a message, you can