summaryrefslogtreecommitdiffhomepage
path: root/src/srp
diff options
context:
space:
mode:
authorThomas Voss <mail@thomasvoss.com> 2023-11-14 03:01:06 +0100
committerThomas Voss <mail@thomasvoss.com> 2023-11-14 03:01:06 +0100
commitb08105bfe7a5aa1e8467dae84601a585f490318a (patch)
tree2edc38722a7bbd2c070c8b0207c3bfdc1856b36d /src/srp
parentebb2e8d6e7a981bf35c5df6d5b4ce5d9ec0429cb (diff)
Use single quotes
Diffstat (limited to 'src/srp')
-rw-r--r--src/srp/fw-ec/index.gsp4
-rw-r--r--src/srp/fw-ec/kbd-sc-cb.c.gsp2
-rw-r--r--src/srp/gsp/index.gsp4
3 files changed, 5 insertions, 5 deletions
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