Fix a typo in a blog post

diff --git a/source/posts/2023-04-08-making-shell-scripts-executable-just-in-time.org b/source/posts/2023-04-08-making-shell-scripts-executable-just-in-time.org
index 0ff25017648f139915b08b39659ac35505073b3c..f6878ab89febef96d57f25af36a647189703d99f 100644 (file)
--- a/source/posts/2023-04-08-making-shell-scripts-executable-just-in-time.org
+++ b/source/posts/2023-04-08-making-shell-scripts-executable-just-in-time.org
@@ -103,11 +103,11 @@ C-x v h~ reveals the following commit:
 #+end_src
 
 As we see in the above patch, back in 2000 this function would simply
-look at the start of your buffer, and if begins with a /shebang/ it'd
-ensure that the file has executable permissions.  Other than the name
-of the function becoming yet a little longer (the ~executable-~ prefix
-was added, so to follow Elisp namespacing conventions), not much has
-changed in terms of its implementation since then.
+look at the start of your buffer, and if it finds there a /shebang/
+it'd ensure that the file has executable permissions.  Other than the
+name of the function becoming yet a little longer (the ~executable-~
+prefix was added, so to follow Elisp namespacing conventions), not
+much has changed in terms of its implementation since then.
 
 Although, as I described earlier, putting
 ~executable-make-buffer-file-executable-if-script-p~ into one's