From efc2bca752a4c76b1ff6a73fa1f889762f170a07 Mon Sep 17 00:00:00 2001 From: Thomas Voss Date: Mon, 23 Sep 2024 06:03:26 +0200 Subject: Fix typos --- src/blog/windowing/index.gsp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/blog/windowing/index.gsp') 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 -- cgit v1.2.3