Use American English spelling throughout

This commit is contained in:
2026-09-15 11:45:58 -07:00
parent 6ba89696ee
commit d1731efdb9
169 changed files with 786 additions and 795 deletions
+3 -3
View File
@@ -75,7 +75,7 @@ describe("what the signature is allowed to mean", () => {
expect(shouldRemember(report)).toBe(true);
});
it("the same certificate again is recognised", async () => {
it("the same certificate again is recognized", async () => {
const crypto = await verifyMessage(fixture("signed-rsa.eml"));
if (crypto.kind !== "intact") throw new Error("fixture should verify");
const known: KnownSigner = { fingerprint: crypto.cert.fingerprint, name: "Ada Lovelace", firstSeen: "2026-09-01T00:00:00Z" };
@@ -129,7 +129,7 @@ describe("matching a certificate to an address", () => {
});
});
describe("canonicalisation", () => {
describe("canonicalization", () => {
it("turns a lone LF into CRLF and leaves an existing CRLF alone", () => {
const mixed = new TextEncoder().encode("a\nb\r\nc\n");
expect(new TextDecoder().decode(toCanonicalCrlf(mixed))).toBe("a\r\nb\r\nc\r\n");
@@ -141,7 +141,7 @@ describe("canonicalisation", () => {
});
/*
* The reason canonicalisation is applied at all: a store that hands back a
* The reason canonicalization is applied at all: a store that hands back a
* message with bare LFs would otherwise fail every signature it holds, and
* the message would look identical on screen while doing it.
*/
+1 -1
View File
@@ -3,7 +3,7 @@
*
* This works on bytes, not on a string, and that is the whole point. A
* signature is over an octet sequence: decode it to text, re-encode it, or let
* anything normalise a line ending on the way past, and the digest changes
* anything normalize a line ending on the way past, and the digest changes
* while the message still looks identical on screen. Every part here keeps a
* subarray of the original buffer rather than a rebuilt copy.
*
+1 -1
View File
@@ -19,7 +19,7 @@
* without a certificate authority anywhere in the picture.
*
* So nothing here ever renders the bare word "verified". The caller is given
* the crypto result and the trust judgement separately, and has to say both.
* the crypto result and the trust judgment separately, and has to say both.
*/
import { parseSignedData, type SignerInfo } from "./cms";
import { decodeTransfer, findPart, parseMime, toCanonicalCrlf, type MimePart } from "./mime";