Double word:
In the section "11.3.6.2 fcTL Frame Control Chunk"
There is a part that says "Exactly one fcTL chunk chunk is required for each frame"
Small improvements:
-
In the section "4.9.1 Structure" the term "default image" is used for the first time to refer to a concept that already had a name since the section "3. Terms, definitions, and abbreviated terms", the term being "static image". "Default image" is used only 5 times, so I think sticking to "static image" is more consistent.
-
In the section "4.9.1 Structure" there is a part that says "The boundaries of the entire animation are specified by the width and height parameters of the IHDR chunk". Instead of "parameters" I think it's better to say "fields". There are other instances in which "parameter" is used instead of "field":
4.9.3 Output buffer
11.3.4.4 sPLT Suggested palette ("[...]as the keyword parameter for the tEXt chunk")
Double word:
In the section "11.3.6.2 fcTL Frame Control Chunk"
There is a part that says "Exactly one fcTL chunk chunk is required for each frame"
Small improvements:
In the section "4.9.1 Structure" the term "default image" is used for the first time to refer to a concept that already had a name since the section "3. Terms, definitions, and abbreviated terms", the term being "static image". "Default image" is used only 5 times, so I think sticking to "static image" is more consistent.
In the section "4.9.1 Structure" there is a part that says "The boundaries of the entire animation are specified by the width and height parameters of the IHDR chunk". Instead of "parameters" I think it's better to say "fields". There are other instances in which "parameter" is used instead of "field":
4.9.3 Output buffer
11.3.4.4 sPLT Suggested palette ("[...]as the keyword parameter for the tEXt chunk")