Typos in comments

This commit is contained in:
Jay Berkenbilt 2021-12-01 14:34:19 -05:00
parent c75577f9d6
commit 73d70902e0
3 changed files with 8 additions and 3 deletions

View File

@ -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",

View File

@ -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

View File

@ -535,7 +535,7 @@ extern "C" {
* 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