From 60077e502c54af3de5cb11cbbdef7e686618bdeb Mon Sep 17 00:00:00 2001 From: Josh Aas Date: Mon, 9 Feb 2026 09:55:15 -0500 Subject: [PATCH] Fix typos --- content/en/docs/a-warm-welcome-to-asn1-and-der.md | 2 +- content/en/docs/glossary.md | 8 ++++---- content/en/docs/profiles.md | 2 +- content/en/post/2020-09-17-new-root-and-intermediates.md | 2 +- content/en/post/2022-2-25-ford-foundation.md | 2 +- 5 files changed, 8 insertions(+), 8 deletions(-) diff --git a/content/en/docs/a-warm-welcome-to-asn1-and-der.md b/content/en/docs/a-warm-welcome-to-asn1-and-der.md index 78bb64f893..69a037a7fa 100644 --- a/content/en/docs/a-warm-welcome-to-asn1-and-der.md +++ b/content/en/docs/a-warm-welcome-to-asn1-and-der.md @@ -989,7 +989,7 @@ Here is the encoding of a SEQUENCE OF INTEGER containing the numbers 7, SET encoding ------------ -Like SEQUENCE, a SET is Contructed, meaning that its value bytes are the +Like SEQUENCE, a SET is Constructed, meaning that its value bytes are the concatenation of its encoded fields. Its tag number is 0x11. Since the [Constructed vs Primitive](#constructed-vs-primitive) bit (bit 6) is always set to 1, that means it's encoded with a tag byte of 0x31. diff --git a/content/en/docs/glossary.md b/content/en/docs/glossary.md index 1633bc2534..00451ec53e 100644 --- a/content/en/docs/glossary.md +++ b/content/en/docs/glossary.md @@ -61,7 +61,7 @@ Note for translators: {{% def id="CRL" name="Certificate Revocation List" abbr="CRL" %}} A method to inform [user agents](#def-user-agent) about the [revocation](#def-revocation) status of a [certificate](#def-leaf). This is a list of the serial numbers of all revoked certificates from a given CA, signed by that CA. [Wikipedia](https://en.wikipedia.org/wiki/Certificate_revocation_list) {{% /def %}} -{{% def id="CSR" name="Certificate Signing Request" abbr="CSR" %}} A signed file containing the needed information required by the [CA](#def-CA) to generated a certificate. Relevant information for [Let's Encrypt](#def-LE) are the [Common Name](#def-CN), [Subject Alternative Names](#def-SAN), and Subject Public Key Info. Usually, [client applications](#def-ACME-client) automatically generate the CSR for the user, although a web hosting provider or device might also generate a CSR. [Wikipedia](https://en.wikipedia.org/wiki/Certificate_signing_request) {{% /def %}} +{{% def id="CSR" name="Certificate Signing Request" abbr="CSR" %}} A signed file containing the needed information required by the [CA](#def-CA) to generate a certificate. Relevant information for [Let's Encrypt](#def-LE) are the [Common Name](#def-CN), [Subject Alternative Names](#def-SAN), and Subject Public Key Info. Usually, [client applications](#def-ACME-client) automatically generate the CSR for the user, although a web hosting provider or device might also generate a CSR. [Wikipedia](https://en.wikipedia.org/wiki/Certificate_signing_request) {{% /def %}} {{% def id="store" name="Certificate Store" %}} A certificate store contains a list of trusted [roots](#def-root). Operating systems (such as Windows, Android or Debian) and [web browsers](#def-web-browser) (such as Firefox) maintain a certificate store. Browsers without one rely on the operating systems' certificate store. [Certificates](#def-leaf) provided by [Let's Encrypt](#def-LE) are [trusted by most certificates stores](/certificates). {{% /def %}} @@ -87,7 +87,7 @@ Note for translators: {{% def id="EdDSA" name="Edwards-curve Digital Signature Algorithm" abbr="EdDSA" abbr_first="1" %}} A modern public-key signature system based on elliptic curves, designed to solve several common [implementation issues](https://ed25519.cr.yp.to/) with elliptic curve cryptography. Certificate Authorities like [Let's Encrypt](#def-LE) can't provide EdDSA certificates yet. [Wikipedia](https://en.wikipedia.org/wiki/EdDSA) {{% /def %}} -{{% def id="ECC" name="Elliptic Curve Cryptography" abbr="ECC" %}} An type of public-key cryptography based on elliptic curves. ECC uses smaller keys compared to non-EC cryptography while providing equivalent security. [Cloudflare](https://blog.cloudflare.com/a-relatively-easy-to-understand-primer-on-elliptic-curve-cryptography/) - [Wikipedia](https://en.wikipedia.org/wiki/Elliptic-curve_cryptography) {{% /def %}} +{{% def id="ECC" name="Elliptic Curve Cryptography" abbr="ECC" %}} A type of public-key cryptography based on elliptic curves. ECC uses smaller keys compared to non-EC cryptography while providing equivalent security. [Cloudflare](https://blog.cloudflare.com/a-relatively-easy-to-understand-primer-on-elliptic-curve-cryptography/) - [Wikipedia](https://en.wikipedia.org/wiki/Elliptic-curve_cryptography) {{% /def %}} {{% def id="EV" name="Extended Validation" abbr="EV" %}} A type of certificate validation for which the [CA](#def-CA) has verified the legal entity controlling the website. They contain information about that entity. Controls from the [CA](#def-CA) are more strict than for [OV](#def-OV) certificates. [Let's Encrypt](#def-LE) doesn't offer EV certificates. [Wikipedia](https://en.wikipedia.org/wiki/Extended_Validation_Certificate) {{% /def %}} @@ -141,7 +141,7 @@ Note for translators: {{% def id="root" name="Root certificate" %}} A [self-signed](#def-self-signed) certificate controlled by a [certificate authority](#def-CA), used to sign its [intermediate](#def-intermediate) certificates and included in [certificate stores](#def-store). [Wikipedia](https://en.wikipedia.org/wiki/Root_certificate) {{% /def %}} -{{% def id="root-program" name="Root Program" %}} The policies an organization uses to decide which certificates to include in its [certificate store](#def-store), and thereforce which CAs are trusted by their software. {{% /def %}} +{{% def id="root-program" name="Root Program" %}} The policies an organization uses to decide which certificates to include in its [certificate store](#def-store), and therefore which CAs are trusted by their software. {{% /def %}} {{% def id="RSA" abbr="RSA" %}} A public-key algorithm used for encryption and to digitally sign certificates. [Wikipedia](https://en.wikipedia.org/wiki/RSA_(cryptosystem)) {{% /def %}} @@ -161,7 +161,7 @@ Note for translators: {{% def id="TLD" name="Top-Level Domain" abbr="TLD" %}} Highest level in the hierarchical Domain Name System, such as country-code top-level domains (ccTLDs) like `.de` (Germany), `.cn` (China) and generic top-level domains (gTLDs) like `.com`, `.org`. [Wikipedia](https://en.wikipedia.org/wiki/Top-level_domain) {{% /def %}} -{{% def id="TLS" name="Transport-Level Security" abbr="TLS" abbr_first="1" %}} The protocol used by HTTPS to encrypt and authenticate web page visits. {{% /def %}} +{{% def id="TLS" name="Transport-Layer Security" abbr="TLS" abbr_first="1" %}} The protocol used by HTTPS to encrypt and authenticate web page visits. {{% /def %}} {{% def id="TLSA" abbr="TLSA" %}} The part of [DANE](#def-DANE) specifically related to validating [TLS](#def-TLS) connections. {{% /def %}} diff --git a/content/en/docs/profiles.md b/content/en/docs/profiles.md index 34b4443954..536a8d207b 100644 --- a/content/en/docs/profiles.md +++ b/content/en/docs/profiles.md @@ -131,7 +131,7 @@ The process for selecting a profile is described in [this Internet-Draft](https: In general, if you want to select a profile, you should: -1. Read your ACME client's documentation to see if it support profile selection, and if it does, how to tell it which profile you want. +1. Read your ACME client's documentation to see if it supports profile selection, and if it does, how to tell it which profile you want. 2. Fetch the Let's Encrypt [production](https://acme-v02.api.letsencrypt.org/directory) or [staging](https://acme-staging-v02.api.letsencrypt.org/directory) directory object to see which profiles are available. 3. Configure your desired profile within your ACME client. diff --git a/content/en/post/2020-09-17-new-root-and-intermediates.md b/content/en/post/2020-09-17-new-root-and-intermediates.md index cd2277da4b..d9f77ee646 100644 --- a/content/en/post/2020-09-17-new-root-and-intermediates.md +++ b/content/en/post/2020-09-17-new-root-and-intermediates.md @@ -189,7 +189,7 @@ to issue an OCSP responder signed by ISRG Root X2. # Putting It All Together -Now that we’ve shared our new certificates look the way they do, there’s one +Now that we've shared why our new certificates look the way they do, there’s one last thing we’d like to mention: how we actually went about issuing them. The creation of new root and intermediate certificates is a big deal, since diff --git a/content/en/post/2022-2-25-ford-foundation.md b/content/en/post/2022-2-25-ford-foundation.md index aec4fab6f9..4b5d762a0b 100644 --- a/content/en/post/2022-2-25-ford-foundation.md +++ b/content/en/post/2022-2-25-ford-foundation.md @@ -18,7 +18,7 @@ excerpt: "$1M grant from The Ford Foundation supports ISRG’s security and priv The Internet has considerable potential to help build a more just, equitable, and sustainable world for all people. Yet for everyone online—and indeed the billions not yet online—barriers to secure and privacy-respecting communication remain pervasive. -ISRG was founded in 2013 to find and eliminate these barriers. Today, we’re proud to announce a $1M grant from the Ford Foundation to continue our efforts. +ISRG was founded in 2013 to find and eliminate these barriers. Today, we’re proud to announce a $1M grant from the Ford Foundation to continue our efforts. Our first project, Let’s Encrypt, leverages technology whose foundation has existed for nearly three decades—TLS certificates for securely communicating information via HTTP. Yet even for people well-versed in technology, adopting TLS proved daunting.