From 81c96702260fe5068622ea87a0f29e5d626d22a7 Mon Sep 17 00:00:00 2001 From: Sean Purcell Date: Thu, 26 Jan 2017 11:15:34 -0800 Subject: [PATCH] Fixed commented issues --- doc/zstd_compression_format.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/zstd_compression_format.md b/doc/zstd_compression_format.md index 03a970c16..eb5c1ca7e 100644 --- a/doc/zstd_compression_format.md +++ b/doc/zstd_compression_format.md @@ -380,9 +380,9 @@ There are 4 block types : This value cannot be used with current version of this specification. Block sizes must respect a few rules : -- In compressed mode, `compressed size` is always strictly `< decompressed size`. -- Block decompressed size is always <= maximum back-reference distance . -- Block decompressed size is always <= 128 KB +- In compressed mode, compressed size is always strictly less than decompressed size. +- Block decompressed size is always <= maximum back-reference distance. +- Block decompressed size is always <= 128 KB. __`Block_Content`__ @@ -580,7 +580,7 @@ which describes how to decode the list of weights. - if `headerByte` >= 128 : this is a direct representation, where each `Weight` is written directly as a 4 bits field (0-15). They are encoded forward, 2 weights to a byte with the first weight taking - the top 4 bits and the second taking the bottom two (e.g. + the top four bits and the second taking the bottom four (e.g. `Weight[0] = (Byte[0] >> 4), Weight[1] = (Byte[0] & 0xf)`, etc.). The full representation occupies `((Number_of_Symbols+1)/2)` bytes, meaning it uses a last full byte even if `Number_of_Symbols` is odd.