felixfoertsch/syncthing
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 10 Wiki Activity

spelling-fixes

Browse Source
This commit is contained in:
ka7
2016-05-08 10:20:20 +01:00
committed by Audrius Butkevicius
parent bdafe9f5d4
commit 7eacdaa11b
7 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
specs/bep-v1.rst
+2 -2
View File
@@ -190,7 +190,7 @@ For C=1:
- The Length field contains the length, in bytes, of the compressed
message data plus a four byte uncompressed length field.
- The compressed message data is preceeded by a 32 bit field denoting
- The compressed message data is preceded by a 32 bit field denoting
the length of the uncompressed message.
- The message data is compressed using the LZ4 format and algorithm
@@ -1022,7 +1022,7 @@ is no longer available, therefore the list of block indexes should be truncated.
Messages with **Forget** bit set MUST NOT have any block indexes.
Any update message which is being sent for a different **Version** of the same
file name must be preceeded with an update message for the old version of that
file name must be preceded with an update message for the old version of that
file with the **Forget** bit set.
As a safeguard on the receiving side, value of **Version** changing between
specs/globaldisco-v3.rst
+2 -2
View File
@@ -33,7 +33,7 @@ certificate was presented, status ``403`` (Forbidden) is returned. If the
posted data doesn't conform to the expected format, ``400`` (Bad Request) is
returned.
In successfull responses, the server may return a ``Reannounce-After`` header
In successful responses, the server may return a ``Reannounce-After`` header
containing the number of seconds after which the client should perform a new
announcement.
@@ -52,7 +52,7 @@ Queries are performed as HTTPS GET requests to the announce server URL. The
requested device ID is passed as the query parameter "device", in canonical
string form, i.e. ``https://announce.syncthing.net/?device=ABC12345-....``
Successfull responses will have status code ``200`` (OK) and carry a JSON payload
Successful responses will have status code ``200`` (OK) and carry a JSON payload
of the same format as the announcement above. The response will not contain
empty or unspecified addresses.
specs/relay-v1.rst
+1 -1
View File
@@ -157,7 +157,7 @@ Client B - Temporary protocol mode
Messages
--------
All messages are preceeded by a header message. Header message contains the
All messages are preceded by a header message. Header message contains the
magic value 0x9E79BC40, message type integer, and message length.
.. warning::