diff --git a/docs/Reticulum Manual.pdf b/docs/Reticulum Manual.pdf index 29e1d07..6d6b2f2 100644 Binary files a/docs/Reticulum Manual.pdf and b/docs/Reticulum Manual.pdf differ diff --git a/docs/manual/_sources/understanding.rst.txt b/docs/manual/_sources/understanding.rst.txt index 6d4bf27..1a6fd7f 100644 --- a/docs/manual/_sources/understanding.rst.txt +++ b/docs/manual/_sources/understanding.rst.txt @@ -618,8 +618,8 @@ times and priorities described earlier in this chapter. .. _understanding-packetformat: -Binary Packet Format --------------------- +Wire Format +----------- .. code-block:: text @@ -710,7 +710,7 @@ Binary Packet Format The following table lists example sizes of various packet types. The size listed are the complete on- - wire size including all fields. + wire size counting all fields including headers. - Path Request : 33 bytes - Announce : 151 bytes diff --git a/docs/manual/index.html b/docs/manual/index.html index ab3941b..5fdfb8d 100644 --- a/docs/manual/index.html +++ b/docs/manual/index.html @@ -123,7 +123,7 @@ to participate in the development of Reticulum itself.
Requests a path to the destination from the network. If another reachable peer on the network knows a path, it will announce it.
destination_hash – A destination hash as bytes.
+destination_hash – A destination hash as bytes.
on_interface – If specified, the path request will only be sent on this interface. In normal use, Reticulum handles this automatically, and this parameter should not be used.
== Reticulum Wire Format ======
A Reticulum packet is composed of the following fields:
@@ -769,7 +769,7 @@ proof 11
The following table lists example sizes of various
packet types. The size listed are the complete on-
- wire size including all fields.
+ wire size counting all fields including headers.
- Path Request : 33 bytes
- Announce : 151 bytes
@@ -818,7 +818,7 @@ proof 11