by a password → with a password
can't → unable to
retrieven → retrieved

Change-Id: Ibd19a74d9137a5065f56674e42dcfbfa2939815e
This commit is contained in:
ovari123 2024-12-02 00:49:44 -04:00
parent 6adb93157f
commit c64603c36f
2 changed files with 4 additions and 4 deletions

View File

@ -41,7 +41,7 @@ In cx.ring.Ring.ConfigurationManager:
</method>
```
The details can be retrieven from the method `getAccountTemplate(type)` with `type=JAMI` or `type=SIP`. For example, this is the following code used in LRC.
The details can be retrieved from the method `getAccountTemplate(type)` with `type=JAMI` or `type=SIP`. For example, this is the following code used in LRC.
```cpp
std::string

View File

@ -58,8 +58,8 @@ For contacts, no circle means that no device is detected on the DHT. This contac
is unreachable. If an orange circle is present, this means that at least a device
is announced on the DHT, so this contact SEEMS to be reachable. You do not have
a direct connection towards this peer yet. But they should be able to receive
connection requests. Because the device is not directly connected to anything, we
can't determine for sure the status of this device. So this can be translated to
connection requests. Because the device is not directly connected to anything, the
device status is unable to be determine for sure. So this can be translated to
"Seems to be reachable", but connection may fail (firewall, deadlock, NAT, etc).
The presence generally have a TTL of 10 min over the DHT and several hours if push notifications are enabled.
@ -380,7 +380,7 @@ What happens when I link a new device?
When you link a device to your account, your :ref:`account archive
<developer/technical-overview:Jami archive (export.gz)>` is put on the
Jami network for a few minutes. It is protected by a password Jami
Jami network for a few minutes. It is protected with a password Jami
gives you.
The new device receives your full account certificate with the master