aboutsummaryrefslogtreecommitdiffstats
path: root/include/qpdf/JSON.hh
diff options
context:
space:
mode:
authorm-holger <m-holger@kubitscheck.org>2022-02-02 15:31:33 +0100
committerJay Berkenbilt <jberkenbilt@users.noreply.github.com>2022-02-02 21:07:32 +0100
commite813176bc02c32e26e109a1b86333ae181cc0601 (patch)
tree0620b581bc203309432f5db7b754e5cc1722b378 /include/qpdf/JSON.hh
parentbc6403708cb0c34e684f3b88701c7534837a2581 (diff)
downloadqpdf-e813176bc02c32e26e109a1b86333ae181cc0601.tar.zst
Fix some doc typos
Diffstat (limited to 'include/qpdf/JSON.hh')
-rw-r--r--include/qpdf/JSON.hh8
1 files changed, 4 insertions, 4 deletions
diff --git a/include/qpdf/JSON.hh b/include/qpdf/JSON.hh
index d45fb3e1..4ec53f2f 100644
--- a/include/qpdf/JSON.hh
+++ b/include/qpdf/JSON.hh
@@ -25,12 +25,12 @@
// This is a simple JSON serializer and parser, primarily designed for
// serializing QPDF Objects as JSON. While it may work as a
// general-purpose JSON parser/serializer, there are better options.
-// JSON objects contain their data as smart pointers. One JSON object
+// JSON objects contain their data as smart pointers. When one JSON object
// is added to another, this pointer is copied. This means you can
// create temporary JSON objects on the stack, add them to other
// objects, and let them go out of scope safely. It also means that if
-// the json JSON object is added in more than one place, all copies
-// share underlying data. This makes them similar in structure and
+// a JSON object is added in more than one place, all copies
+// share the underlying data. This makes them similar in structure and
// behavior to QPDFObjectHandle and may feel natural within the QPDF
// codebase, but it is also a good reason not to use this as a
// general-purpose JSON package.
@@ -105,7 +105,7 @@ class JSON
//
// * The schema is a nested structure containing dictionaries,
// single-element arrays, and strings only.
- // * Recursively walk the schema
+ // * Recursively walk the schema.
// * If the current value is a dictionary, this object must have
// a dictionary in the same place with the same keys. If flags
// contains f_optional, a key in the schema does not have to