trivial: typos

Author: ximion

content/docs/tsync-format.md

@@ -76,12 +76,12 @@ hashing algorithm to ensure data has not been accidentally corrupted.
 
 ## Header
 
-All data in a tsync file are stored in as little-endian.
-All values written to the header block are hashed using the XXH3 hashing algorithm.
+All data in a tsync file are stored as little-endian.
+All values written to the header block are hashed using the XXH3 hashing algorithm as well.
 
 A tsync file always begins with magic number `TSYNC_FILE_MAGIC` as a `uint64` number, followed
 by `TSYNC_FILE_VERSION_MAJOR` and `TSYNC_FILE_VERSION_MINOR` as `uint64` as well.
-These two alues are followed by the creation date of the tsync file as UNIX timestamp in `int64` format.
+These two values are followed by the creation date of the tsync file as UNIX timestamp in `int64` format.
 
 These values are followed by the module name that created the tsync file as null-terminated UTF-8 encoded string.
 The module name is followed by the experiment collection ID (EDL collection ID) as null-terminated UTF-8 encoded
@@ -98,7 +98,7 @@ are checksummed together. The block sizes denotes the count of values each block
 128 or 256, but could be any value depending on the desired speed/robustness/size tradeoffs.
 
 The block size is followed by the name of the first time as UTF-8, zero-terminated string. This could be a value
-like `"master clock"`. After this value follows the time unit ID `TSyncFileTimeUnit` as `uint16` value to
+like `"master clock"`. After this value follows the time unit identifier `TSyncFileTimeUnit` as `uint16` value to
 denote the unit of measurement, followed by the byte size of the values this data unit is stored in as denoted
 by the `TSyncFileDataType` enum, as `uint16`.
 
@@ -125,5 +125,5 @@ After writing the block, the rolling checksum is reset, and the next block is wr
 (This allows to pinpoint and ignore a damaged block, if the file gets corrupted, without loosing all data).
 
 If the file is to be finished, but the last block did not end with a terminator yet, a `TSYNC_FILE_BLOCK_TERM`
-terminator value and the respective checksum is written enayway, ignoring the block size, so that a complete tsync file
+terminator value and the respective checksum is written anyway, ignoring the block size, so that a complete tsync file
 always ends with a terminator+checksum combination.