aboutsummaryrefslogtreecommitdiffstats
path: root/libqpdf/NNTree.cc
diff options
context:
space:
mode:
authorm-holger <m-holger@kubitscheck.org>2023-05-29 20:26:18 +0200
committerm-holger <m-holger@kubitscheck.org>2023-06-02 20:24:12 +0200
commitacd0acf16931ce92bc908e4960c5a1e43d53b550 (patch)
tree466c87d625ab4d5b3eab45301fab34e11be1271a /libqpdf/NNTree.cc
parent3c5700c255f4603b5df9c6d183d13dd71a083cc3 (diff)
downloadqpdf-acd0acf16931ce92bc908e4960c5a1e43d53b550.tar.zst
Fix doc typos
Diffstat (limited to 'libqpdf/NNTree.cc')
-rw-r--r--libqpdf/NNTree.cc10
1 files changed, 5 insertions, 5 deletions
diff --git a/libqpdf/NNTree.cc b/libqpdf/NNTree.cc
index 129c8734..a584ff8d 100644
--- a/libqpdf/NNTree.cc
+++ b/libqpdf/NNTree.cc
@@ -44,10 +44,10 @@ NNTreeIterator::updateIValue(bool allow_invalid)
// various cases to ensure we don't introduce that bug in the future, but sadly it's tricky to
// verify by reasoning about the code that this constraint is always satisfied. Whenever we
// update what the iterator points to, we should call setItemNumber, which calls this. If we
- // change what the iterator in some other way, such as replacing a value or removing an item and
- // making the iterator point at a different item in potentially the same position, we must call
- // updateIValue as well. These cases are handled, and for good measure, we also call
- // updateIValue in operator* and operator->.
+ // change what the iterator points to in some other way, such as replacing a value or removing
+ // an item and making the iterator point at a different item in potentially the same position,
+ // we must call updateIValue as well. These cases are handled, and for good measure, we also
+ // call updateIValue in operator* and operator->.
bool okay = false;
if ((item_number >= 0) && this->node.isDictionary()) {
@@ -226,7 +226,7 @@ NNTreeIterator::split(QPDFObjectHandle to_split, std::list<PathElement>::iterato
// Split some node along the path to the item pointed to by this iterator, and adjust the
// iterator so it points to the same item.
- // In examples, for simplicity, /Nums is show to just contain numbers instead of pairs. Imagine
+ // In examples, for simplicity, /Nums is shown to just contain numbers instead of pairs. Imagine
// this tree:
//
// root: << /Kids [ A B C D ] >>