aboutsummaryrefslogtreecommitdiffstats
path: root/manual/design.rst
diff options
context:
space:
mode:
authorm-holger <m-holger@kubitscheck.org>2022-03-12 17:48:21 +0100
committerJay Berkenbilt <jberkenbilt@users.noreply.github.com>2022-03-12 20:10:43 +0100
commitb8ec4395e740303c7046667f0c34478c8522520f (patch)
treef84f95a2a7c0d263fe0019dc7785a8925276a81c /manual/design.rst
parent09a36ad62bfa787642778b8076ae5b4ba4a64fcc (diff)
downloadqpdf-b8ec4395e740303c7046667f0c34478c8522520f.tar.zst
Minor manual fixes
Diffstat (limited to 'manual/design.rst')
-rw-r--r--manual/design.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/manual/design.rst b/manual/design.rst
index f323aa75..07aaa875 100644
--- a/manual/design.rst
+++ b/manual/design.rst
@@ -105,7 +105,7 @@ and then reads the cross reference tables and trailer dictionaries. The
read all of them so it can check the ``/Prev`` key. ``QPDF`` class users
may request the root object and the trailer dictionary specifically. The
cross reference table is kept private. Objects may then be requested by
-number of by walking the object tree.
+number or by walking the object tree.
When a PDF file has a cross-reference stream instead of a
cross-reference table and trailer, requesting the document's trailer
@@ -254,7 +254,7 @@ resulting ``QPDFObjectHandle``. The calling object handle then replaces
its ``PointerHolder<QDFObject>`` with the one from the newly returned
``QPDFObjectHandle``. In this way, only a single copy of any direct
object need exist and clients can access objects transparently without
-knowing caring whether they are direct or indirect objects.
+knowing or caring whether they are direct or indirect objects.
Additionally, no object is ever read from the file more than once. That
means that only the portions of the PDF file that are actually needed
are ever read from the input file, thus allowing the qpdf package to
@@ -264,7 +264,7 @@ If the requested object is inside of an object stream, the object stream
itself is first read into memory. Then the tokenizer reads objects from
the memory stream based on the offset information stored in the stream.
Those individual objects are cached, after which the temporary buffer
-holding the object stream contents are discarded. In this way, the first
+holding the object stream contents is discarded. In this way, the first
time an object in an object stream is requested, all objects in the
stream are cached.