Skip to content

Commit 69299e1

Browse files
dericedmichaelni
authored andcommitted
backtick quote use of defined terms
Github: Closes #87 Signed-off-by: Michael Niedermayer <[email protected]>
1 parent e7d3abb commit 69299e1

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

ffv1.md

+6-6
Original file line numberDiff line numberDiff line change
@@ -28,9 +28,9 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "S
2828
-------- --------------------------------------------------------------
2929
`Container`: Format that encapsulates `Frames` and (when required) a `Configuration Record` into a bitstream.
3030

31-
`Sample`: The smallest addressable representation of a color component or a luma component in a frame. Examples of sample are Luma, Blue Chrominance, Red Chrominance, Alpha, Red, Green, and Blue.
31+
`Sample`: The smallest addressable representation of a color component or a luma component in a `Frame`. Examples of sample are Luma, Blue Chrominance, Red Chrominance, Alpha, Red, Green, and Blue.
3232

33-
`Pixel`: The smallest addressable representation of a color in a frame. It is composed of 1 or more samples.
33+
`Pixel`: The smallest addressable representation of a color in a `Frame`. It is composed of 1 or more samples.
3434

3535
`ESC`: An ESCape symbol to indicate that the symbol to be stored is too large for normal storage and that an alternate storage method.
3636

@@ -169,13 +169,13 @@ The FFV1 bitstream is described in this document using pseudo-code. Note that th
169169

170170
### NumBytes
171171

172-
`NumBytes` is a non-negative integer that expresses the size in 8-bit octets of particular FFV1 `Configuration Record` or `Frame`. FFV1 relies on its container to store the `NumBytes` values, see [the section on the `Mapping FFV1 into Containers`](#mapping-ffv1-into-containers).
172+
`NumBytes` is a non-negative integer that expresses the size in 8-bit octets of particular FFV1 `Configuration Record` or `Frame`. FFV1 relies on its `Container` to store the `NumBytes` values, see [the section on the `Mapping FFV1 into Containers`](#mapping-ffv1-into-containers).
173173

174174
### Bitstream functions
175175

176176
#### remaining_bits_in_bitstream
177177

178-
`remaining_bits_in_bitstream( )` means the count of remaining bits after the pointer in that Configuration Record or Frame. It is computed from the `NumBytes` value multiplied by 8 minus the count of bits of that Configuration Record or Frame already read by the bitstream parser.
178+
`remaining_bits_in_bitstream( )` means the count of remaining bits after the pointer in that `Configuration Record` or `Frame`. It is computed from the `NumBytes` value multiplied by 8 minus the count of bits of that `Configuration Record` or `Frame` already read by the bitstream parser.
179179

180180
#### byte_aligned
181181

@@ -701,7 +701,7 @@ Default values at the decoder initialization phase:
701701
702702
## Configuration Record
703703
704-
In the case of a FFV1 bitstream with `version >= 3`, a `Configuration Record` is stored in the underlying container, at the track header level. It contains the parameters used for all instances of `Frame`. The size of the `Configuration Record`, `NumBytes`, is supplied by the underlying container.
704+
In the case of a FFV1 bitstream with `version >= 3`, a `Configuration Record` is stored in the underlying `Container`, at the track header level. It contains the parameters used for all instances of `Frame`. The size of the `Configuration Record`, `NumBytes`, is supplied by the underlying `Container`.
705705
706706
```c
707707
pseudo-code | type
@@ -729,7 +729,7 @@ The CRC generator polynomial used is the standard IEEE CRC polynomial (0x104C11D
729729

730730
### Mapping FFV1 into Containers
731731

732-
This `Configuration Record` can be placed in any file format supporting `Configuration Records`, fitting as much as possible with how the file format uses to store `Configuration Records`. The `Configuration Record` storage place and `NumBytes` are currently defined and supported by this version of this specification for the following container formats:
732+
This `Configuration Record` can be placed in any file format supporting `Configuration Records`, fitting as much as possible with how the file format uses to store `Configuration Records`. The `Configuration Record` storage place and `NumBytes` are currently defined and supported by this version of this specification for the following formats:
733733

734734
#### AVI File Format
735735

0 commit comments

Comments
 (0)