summaryrefslogtreecommitdiff
path: root/json.c
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>2014-09-17 06:39:56 -0400
committerEric S. Raymond <esr@thyrsus.com>2014-09-17 06:39:56 -0400
commita8797f6e4ccc7a2fa3e34510e6928c1c2dd95722 (patch)
tree4ac49901f919b99fa9b5b6cc630a081968abcf03 /json.c
parent51b6b93201b1e955fe0310b569ded0514c50b0d5 (diff)
downloadgpsd-a8797f6e4ccc7a2fa3e34510e6928c1c2dd95722.tar.gz
Typo fixes.
Diffstat (limited to 'json.c')
-rw-r--r--json.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/json.c b/json.c
index 8efc4227..9c00b83d 100644
--- a/json.c
+++ b/json.c
@@ -23,8 +23,8 @@ default values to be used when an expected attribute is omitted.
The preceding paragraph told one fib. A single attribute may
actually have a span of multiple specifications with different
syntactically distinguishable types (e.g. string vs. real vs. integer
-vs boolean, but not signed integer vs. unsigned integer or strong vs. map).
-The parser will match the right spec against the actual data.
+vs. boolean, but not signed integer vs. unsigned integer). The parser
+will match the right spec against the actual data.
The dialect this parses has some limitations. First, it cannot
recognize the JSON "null" value. Secondly, arrays may only have