From d5b96abddd2087b0a161b2f2550b8bc48f83b500 Mon Sep 17 00:00:00 2001 From: Shabani Sanel <174913797+Sanel0101@users.noreply.github.com> Date: Sun, 18 Jan 2026 04:49:46 +0100 Subject: [PATCH] Revert "Trim extraneous trailing whitespace in README (#335)" This reverts commit 69a44ef5c17847abb0bb8fbe37354b5aeca82507. --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 2d8784c..004c258 100644 --- a/README.md +++ b/README.md @@ -26,7 +26,7 @@ The static fonts have one file per cut, per family. The variable axes have named ## Texture Healing -Monaspace pioneered the technique of "texture healing" for monospaced fonts: +Monaspace pioneered the technique of "texture healing" for monospaced fonts: ![Texture Healing Example]() @@ -63,7 +63,7 @@ There are ten groups of coding ligatures, separated into stylistic sets. You may * `ss01`: ligatures related to the equals glyph like `!=` and `===`. * `ss02`: ligatures for greater/less or equal (`<=`, `>=`). * `ss03`: ligatures related to arrows like `->` and `~>`. -* `ss04`: ligatures related to markup, like ``. +* `ss04`: ligatures related to markup, like ``. * `ss05`: ligatures related to the F# programming language, like `|>`. * `ss06`: ligatures related to repeated uses of `#`, `+`, and `&`. * `ss07`: ligatures related to colons like `::` or `=:=`. @@ -118,7 +118,7 @@ Font caching on operating systems is an inscrutable mess dating back thirty year - First delete the old fonts… - Then install the new fonts… - Then restart applications that use the fonts… -- … and maybe restart your entire computer. +- … and maybe restart your entire computer. Restarting is usually the only way to be 100% sure that the underlying machinery in the operating system picks up the new fonts.