summaryrefslogtreecommitdiffhomepage
path: root/src/blog
diff options
context:
space:
mode:
Diffstat (limited to 'src/blog')
-rw-r--r--src/blog/extend/index.gsp2
-rw-r--r--src/blog/grab/index.gsp4
-rw-r--r--src/blog/windowing/index.gsp4
3 files changed, 5 insertions, 5 deletions
diff --git a/src/blog/extend/index.gsp b/src/blog/extend/index.gsp
index 069f255..a88a1b4 100644
--- a/src/blog/extend/index.gsp
+++ b/src/blog/extend/index.gsp
@@ -302,7 +302,7 @@ html lang="en" {
another program (such as the @code{-st} terminal) and it adds
tab-support to it. Not only does this reduce code-duplication, but it
also is beneficial for you the software user as it means you get a
- consistent UI with consistent-behavior and -key-bindings wherever you
+ consistent UI with consistent-behaviour and -key-bindings wherever you
go.
}
}
diff --git a/src/blog/grab/index.gsp b/src/blog/grab/index.gsp
index d7974a6..87ebb5f 100644
--- a/src/blog/grab/index.gsp
+++ b/src/blog/grab/index.gsp
@@ -31,7 +31,7 @@ html lang="en" {
p {-
This should be a relatively easy task and for the most part it was, but
I had an issue. Some of these components had some @em{-really} obscure
- properties that could influence their behavior, and seeing as much of
+ properties that could influence their behaviour, and seeing as much of
the codebase was written 10 years ago by utter idiots, the code
implementing these properties is @em{-really} hard to read.
}
@@ -81,7 +81,7 @@ html lang="en" {
component because it’s used everywhere but only a few rare usages
interest me, and it’s not enough to search for just the attribute
because many different components have attributes of the same name (and
- @em{-no} they don’t have the same behavior; the codebase is shit).
+ @em{-no} they don’t have the same behaviour; the codebase is shit).
}
p {-
diff --git a/src/blog/windowing/index.gsp b/src/blog/windowing/index.gsp
index 2493d87..4307ecb 100644
--- a/src/blog/windowing/index.gsp
+++ b/src/blog/windowing/index.gsp
@@ -126,7 +126,7 @@ html lang="en" {
So how do we go from the second image to the third image? The
answer is obvious: we used three windows. Instead of having one
dedicated Emacs window that itself manages two sub-windows, by
- simply breaking it up into two seperate Emacs instances each
+ simply breaking it up into two separate Emacs instances each
displaying only a single file, I allowed my window manager to
make a more informed decision about where to place my web
browser. Intuitively this should make sense; if we have two
@@ -139,7 +139,7 @@ html lang="en" {
p {=
Now we need to keep in mind the usability issues that windowing
in text editors attempt to solve; it is unreasonable to expect
- the user to need to manually and labouriously open a new instance
+ the user to need to manually and laboriously open a new instance
of their text editor, navigate to the project they’re working on,
open a file, etc., all just to view two related files
side-by-side. The reason we all use windowing in our editors is