commit 388a5730f641606121a49bd499b2a647ec0798ea
parent 9eb89cf0a2db9d8fb74b97c31ae6bc8cc4c57936
Author: Jacki <jacki@thejackimonster.de>
Date: Wed, 17 Jun 2026 20:55:08 +0200
minor corrections
Signed-off-by: Jacki <jacki@thejackimonster.de>
Diffstat:
2 files changed, 22 insertions(+), 23 deletions(-)
diff --git a/developers/apis/messenger.rst b/developers/apis/messenger.rst
@@ -37,9 +37,9 @@ The private key can be selected in combination with a name using
gets called every time a message gets sent or received in the room. Once
the handle is initialized you can check your used key pair with
``GNUNET_MESSENGER_get_key`` providing only its public key. The function
-returns NULL if the anonymous key pair is used. If the key pair should
-be replaced with a different one, you can use
-``GNUNET_MESSENGER_set_key`` to ensure proper chaining of used private
+returns NULL if the anonymous key pair is used. If the key pair should
+be replaced with a different one, you can use
+``GNUNET_MESSENGER_set_key`` to ensure proper chaining of used private
keys.
This will automatically cause the handle to send a KEY-message which
@@ -52,8 +52,8 @@ with ``GNUNET_MESSENGER_get_name`` and potentially change or set a name
via ``GNUNET_MESSENGER_set_name``. Any change in name will automatically
be distributed in all entered or opened rooms with a NAME-message.
-In case you have adjusted your name separately in a specific room of
-choice by sending a NAME-message manually, that room will not be
+In case you have adjusted your name separately in a specific room of
+choice by sending a NAME-message manually, that room will not be
affected by the change of your handle's name.
To send a message a message inside of a room you can use
@@ -97,7 +97,7 @@ NAME-message
NAME-messages can be used to change the name (or nick) of your identity
inside a room. The selected name can differ from the identifier used to
-select your private key for signing and decrypting messages.
+select your private key for signing messages.
.. _INVITE_002dmessage:
@@ -127,9 +127,8 @@ FILE-message
------------
FILE-messages can be used to share files inside of a room. They do not
-contain the actual file being shared but its original hash, filename,
-URI to download the file and a symmetric key to decrypt the downloaded
-file.
+contain the actual file being shared but its original hash, filename
+and URI to download the file.
It is recommended to use the FS subsystem and the FILE-messages in
combination.
@@ -160,7 +159,7 @@ TICKET-message
--------------
TICKET-messages can be send privately to other members in the room. The
-member will be able to consume the received ticket via
+member will be able to consume the received ticket via
``GNUNET_RECLAIM_ticket_consume`` to gain access to selected attributes
and their stored values.
@@ -235,11 +234,11 @@ Member sessions
^^^^^^^^^^^^^^^
A member session is a triple of the room key, the member ID and the
-public key of the member's key pair. Member sessions allow that a member
-can change their ID or their private key once at a time without losing
-the ability to delete old messages or identifying the original sender
-of a message. On every change of ID or private key a session will be
-marked as closed. So every session chain will only contain one open
+public key of the member's key pair. Member sessions allow that a member
+can change their ID or their private key once at a time without losing
+the ability to delete old messages or identifying the original sender
+of a message. On every change of ID or private key a session will be
+marked as closed. So every session chain will only contain one open
session with the current ID and public key.
If a session is marked as closed the MESSENGER service will check from
diff --git a/users/messenger.rst b/users/messenger.rst
@@ -68,10 +68,10 @@ through the CADET submodule. You can also optionally leave out the '-r'
parameter and the ROOMKEY to use the zeroed hash instead.
If no IDENTITY is provided you will not send any name to others, you
-will be referred as \"anonymous\" instead and use the anonymous ego (a
-shared key pair known to all peers). If you provide any IDENTITY a
-matching ego will be used to sign your messages. If there is no matching
-ego you will use the anonymous ego instead. The provided IDENTITY will
+will be referred as \"anonymous\" instead and use the anonymous ego (a
+shared key pair known to all peers). If you provide any IDENTITY a
+matching ego will be used to sign your messages. If there is no matching
+ego you will use the anonymous ego instead. The provided IDENTITY will
be distributed as your name for the service in any case.
.. _Opening-a-room:
@@ -125,10 +125,10 @@ Private messaging
As referred in the introduction the service allows sending private
messages with additional end-to-end encryption. These messages will be
visually represented by messages of the kind 'PRIVATE' in case they
-can't be decrypted with your used private key. Members who can't decrypt
-the message can potentially only identify its sender but they can't
-identify its receiver. This prevents other members from collecting more
-metadata than necessary about you.
+can't be decrypted with your accessible stored keys. Members who can't
+decrypt the message can potentially only identify its sender but they
+can't identify its receiver. This prevents other members from collecting
+more metadata than necessary about you.
.. code-block:: text
