From e34dbbfa18ab4753f9637920719e683ba3037fcf Mon Sep 17 00:00:00 2001
From: Jay Berkenbilt <ejb@ql.org>
Date: Sun, 1 May 2022 11:48:41 -0400
Subject: [PATCH] Spell check

---
 TODO                   | 2 ++
 cSpell.json            | 2 +-
 include/qpdf/DLL.h     | 2 +-
 libqpdf/QPDFJob.cc     | 2 ++
 manual/weak-crypto.rst | 6 +++---
 5 files changed, 9 insertions(+), 5 deletions(-)

diff --git a/TODO b/TODO
index 61c3fbfa..0b9d6c4f 100644
--- a/TODO
+++ b/TODO
@@ -39,6 +39,8 @@ Soon: Break ground on "Document-level work"
 Output JSON v2
 ==============
 
+Remember typo: search for "Typo" In QPDFJob::doJSONEncrypt.
+
 Output JSON v2 will contain enough information to completely recreate
 a PDF file. In other words, qpdf will have full, bidirectional,
 lossless json serialization/deserialization of PDF.
diff --git a/cSpell.json b/cSpell.json
index 0a9fe583..fad73cf7 100644
--- a/cSpell.json
+++ b/cSpell.json
@@ -267,7 +267,6 @@
     "mkinstalldirs",
     "mklink",
     "moddate",
-    "moddifyannotations",
     "monoseq",
     "msvc",
     "msvcrt",
@@ -507,6 +506,7 @@
     "unconflicting",
     "underlaying",
     "unencrypted",
+    "unexport",
     "unfilterable",
     "unparse",
     "unpickling",
diff --git a/include/qpdf/DLL.h b/include/qpdf/DLL.h
index 42dc2fac..a29a8d14 100644
--- a/include/qpdf/DLL.h
+++ b/include/qpdf/DLL.h
@@ -63,7 +63,7 @@ for a more in-depth discussion.
 
 * A class's runtime type information is need if the class is going to
   be used as an exception, inherited from, or tested with
-  dynamic_claass. To do these things across a shared object boundary,
+  dynamic_class. To do these things across a shared object boundary,
   runtime type information must be exported.
 
 * On Windows:
diff --git a/libqpdf/QPDFJob.cc b/libqpdf/QPDFJob.cc
index 765e0281..bcaa2ebe 100644
--- a/libqpdf/QPDFJob.cc
+++ b/libqpdf/QPDFJob.cc
@@ -1335,6 +1335,8 @@ QPDFJob::doJSONEncrypt(QPDF& pdf, JSON& j)
         "modifyassembly", JSON::makeBool(pdf.allowModifyAssembly()));
     j_capabilities.addDictionaryMember(
         "modifyforms", JSON::makeBool(pdf.allowModifyForm()));
+    // Typo will be fixed for json v2
+    /* cSpell:ignore moddifyannotations */
     j_capabilities.addDictionaryMember(
         "moddifyannotations", JSON::makeBool(pdf.allowModifyAnnotation()));
     j_capabilities.addDictionaryMember(
diff --git a/manual/weak-crypto.rst b/manual/weak-crypto.rst
index 21d20cad..d61f09b6 100644
--- a/manual/weak-crypto.rst
+++ b/manual/weak-crypto.rst
@@ -32,7 +32,7 @@ hash or two documents with the same hash.
 
 When we say that an encryption algorithm is weak, we either mean that
 a mathematical flaw has been discovered that makes it inherently
-crackable or that it is sufficiently simple that modern computer
+insecure or that it is sufficiently simple that modern computer
 technology makes it possible to use "brute force" to crack. For
 example, when 40-bit keys were originally introduced, it wasn't
 practical to consider trying all possible keys, but today such a thing
@@ -50,7 +50,7 @@ other words, you can't use a weak hash as a digital signature. There
 is no harm, however, in using a weak hash as a way to sort or index
 documents as long as hash collisions are tolerated. It is also common
 to use weak hashes as checksums, which are often used a check that a
-file wasn't damanged in transit or storage, though for true integrity,
+file wasn't damaged in transit or storage, though for true integrity,
 a strong hash would be better.
 
 Note that qpdf must always retain support for weak cryptographic
@@ -138,7 +138,7 @@ MD5 is used in the following non-security-sensitive ways:
 
 It is therefore not possible completely avoid the use of MD5 with
 qpdf, but as long as you are using 256-bit encryption, it is not used
-in a securty-sensitive fashion.
+in a security-sensitive fashion.
 
 .. _breaking-crypto-api: