From b08105bfe7a5aa1e8467dae84601a585f490318a Mon Sep 17 00:00:00 2001 From: Thomas Voss Date: Tue, 14 Nov 2023 03:01:06 +0100 Subject: Use single quotes --- src/srp/fw-ec/index.gsp | 4 ++-- src/srp/fw-ec/kbd-sc-cb.c.gsp | 2 +- src/srp/gsp/index.gsp | 4 ++-- 3 files changed, 5 insertions(+), 5 deletions(-) (limited to 'src/srp') diff --git a/src/srp/fw-ec/index.gsp b/src/srp/fw-ec/index.gsp index 3b8a94a..acd39b9 100644 --- a/src/srp/fw-ec/index.gsp +++ b/src/srp/fw-ec/index.gsp @@ -178,9 +178,9 @@ html lang="en" { aside { p data-ref="1" {- - If you’re confused by what I mean by a “key-chord”, I am simply + If you’re confused by what I mean by a ‘key-chord’, I am simply referring to pressing multiple keys in conjunction, such as when you - press “@kbd{-Ctrl + C}” to copy text. + press ‘@kbd{-Ctrl + C}’ to copy text. } } diff --git a/src/srp/fw-ec/kbd-sc-cb.c.gsp b/src/srp/fw-ec/kbd-sc-cb.c.gsp index fa03466..31524de 100644 --- a/src/srp/fw-ec/kbd-sc-cb.c.gsp +++ b/src/srp/fw-ec/kbd-sc-cb.c.gsp @@ -1,4 +1,4 @@ -@span .c-cmt {-/* “make_code” is the scancode. “pressed” is a boolean that is true if this is a} +@span .c-cmt {-/* ‘make_code’ is the scancode. ‘pressed’ is a boolean that is true if this is a} @span .c-cmt {-keydown event, and false if it’s a keyup. */} r = @span .c-fn {-my_handler_function}(make_code, pressed); diff --git a/src/srp/gsp/index.gsp b/src/srp/gsp/index.gsp index b417165..8c56883 100644 --- a/src/srp/gsp/index.gsp +++ b/src/srp/gsp/index.gsp @@ -86,8 +86,8 @@ html lang="en" { p {- Oh no.} p {- - Now most readers probably had the initial reaction of “@em{-What’s wrong - with Markdown?}”. To answer your question: everything. The issue I + Now most readers probably had the initial reaction of ‘@em{-What’s wrong + with Markdown?}’. To answer your question: everything. The issue I have with these highly-prevalent Markdown-based replacements for m4_abbr(HTML) is that they ignore the fundamental fact that m4_abbr(HTML) and Markdown are @em{-not} compatible languages with each -- cgit v1.2.3