Skip to content

Commit

Permalink
Fix typos
Browse files Browse the repository at this point in the history
  • Loading branch information
gszadovszky committed Nov 4, 2024
1 parent de7f06d commit bc0ba89
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions LogicalTypes.md
Original file line number Diff line number Diff line change
Expand Up @@ -714,9 +714,9 @@ to values. `MAP` must annotate a 3-level structure:
field for map keys and, optionally, a `value` field for map values. It must
not contain any other values.
* The `key` field encodes the map's key type. This field must have
repetition `required` and must always be present. I must be placed at the 0th
position of the `key_value` group. It is suggested to use a primitive as the
type.
repetition `required` and must always be present. It must be placed at the
0th position of the `key_value` group. It is suggested to use a primitive as
the type.
* The `value` field encodes the map's value type and repetition. This field can
be `required`, `optional`, or omitted. It must be placed at the 1st position
of the `key_value` group if present. In case of not present, the map can be
Expand Down Expand Up @@ -751,7 +751,7 @@ be used in existing data and should not be enforced as errors when reading.
Some existing data incorrectly used `MAP_KEY_VALUE` in place of `MAP`. For
backward-compatibility, a group annotated with `MAP_KEY_VALUE` that is not
contained by a `MAP`-annotated group should be handled as a `MAP`-annotated
group. `MAP_KEY_VALUE` may be used for the `kay_value` group.
group. `MAP_KEY_VALUE` may be used for the `key_value` group.

Examples that can be interpreted using these rules:

Expand Down

0 comments on commit bc0ba89

Please sign in to comment.