diff --git a/blog/index.html b/blog/index.html
index 0417499..edaca2e 100644
--- a/blog/index.html
+++ b/blog/index.html
@@ -56,7 +56,7 @@
- Projects
@@ -64,7 +64,7 @@
- Blog
+ Blog
diff --git a/blog/vim_and_ctags.html b/blog/vim_and_ctags.html
index 127f092..357fd79 100644
--- a/blog/vim_and_ctags.html
+++ b/blog/vim_and_ctags.html
@@ -56,7 +56,7 @@
- Projects
@@ -64,7 +64,7 @@
- Blog
+ Blog
@@ -164,7 +164,7 @@ Because I'm not yet a sed/grep expert in the context o
The first option I found for automatically updating the tags file didn't work as advertised: I tried to set up git hooks like Mr.
Pope suggested,
-but for whatever reason the tags file never refreshed on commit. Avoid this rabbit hold! And
+but for whatever reason the tags file never refreshed on commit. Avoid this rabbit hole! And
anyway, don't you want "go to definition" to work between commits too?
- I can now very quickly navigate to where whatever's under my cursor was defined
+ I can now very quickly navigate to the definition of whatever's under my cursor
with a single keystroke. What's nice about this usage of ctags is 1) it runs in the background and never
interrupts you, 2) it's fast, and 3) it runs every time you save.
I haven't tried this at all with JS yet (will be trying gf in normal mode when your curso
- As mentioned above, you can tell vim about multiple tags files in multiple paths. It
+ As alluded to above, you can tell vim about multiple tags files in multiple paths. It
doesn't come up as often that I want to "go to definition" of library code, but I can see how it
might come in handy.