Typos in comments

Jay Berkenbilt
1 parent c75577f9
Showing 3 changed files with 8 additions and 3 deletions
cSpell.json
include/qpdf/QPDFObjectHandle.hh
include/qpdf/qpdf-c.h
@@ -263,6 +263,7 @@
     "onum",
     "opages",
     "opath",
+    "orred",
     "ossl",
     "ostream",
     "ostringstreams",
@@ -308,6 +309,7 @@
     "qpdf",
     "qpdfacroformdocumenthelper",
     "qpdfannotationobjecthelper",
+    "qpdfconstants",
     "qpdfcrypto",
     "qpdfcryptoimpl",
     "qpdfcryptoprovider",
@@ -336,6 +338,7 @@
     "qpdfstreamfilter",
     "qpdfsystemerror",
     "qpdftokenizer",
+    "qpdftypes",
     "qpdfwriter",
     "qpdfx",
     "qpdfxrefentry",
@@ -415,6 +418,7 @@
     "unencrypted",
     "unfilterable",
     "unparse",
+    "unretrieved",
     "upages",
     "upass",
     "urandom",
@@ -320,8 +320,9 @@ class QPDFObjectHandle
     QPDF_DLL
     char const* getTypeName();
  
-    // Exactly one of these will return true for any initialized object.  Operator
-    // and InlineImage are only allowed in content streams.
+    // Exactly one of these will return true for any initialized
+    // object. Operator and InlineImage are only allowed in content
+    // streams.
     QPDF_DLL
     bool isBool();
     QPDF_DLL
@@ -535,7 +535,7 @@ extern &quot;C&quot; {
      * object. All QPDFObjectHandle objects are deleted when they are
      * no longer referenced. Releasing an object handle simply
      * invalidates it. For example, if you create an object,
-     * add it to an existing dictionary or array, and then release it's
+     * add it to an existing dictionary or array, and then release its
      * handle, the object is safely part of the dictionary or array.
      * Similarly, any other object handle refering to the object remains
      * valid. Explicitly releasing an object handle is essentially the