aboutsummaryrefslogtreecommitdiffgithub
diff options
context:
space:
mode:
authorAustin Adams <git@austinjadams.com>2017-03-09 23:38:53 -0500
committerAustin Adams <git@austinjadams.com>2017-03-09 23:38:53 -0500
commit49016e3e83b2ff8d5eb08129d39fdfb481c2bfdf (patch)
treebb84e98db12d3daad9c52a7c7519161fbff4e321
parentcd74b2f8c47154295f74076c3a9e0a4ffa1ec8ca (diff)
downloadwebzone-49016e3e83b2ff8d5eb08129d39fdfb481c2bfdf.tar.gz
webzone-49016e3e83b2ff8d5eb08129d39fdfb481c2bfdf.tar.xz
recent-commits-hugo: Fix typo
-rw-r--r--content/blog/including-recent-commits-hugo.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/content/blog/including-recent-commits-hugo.md b/content/blog/including-recent-commits-hugo.md
index 1a46a32..a7ed1ab 100644
--- a/content/blog/including-recent-commits-hugo.md
+++ b/content/blog/including-recent-commits-hugo.md
@@ -53,8 +53,8 @@ parents!
My first idea for traversal was brute force; that is, looking at every
dang commit in the repository and then sorting them by date. However,
-for gigantic repositories like the Linux kernel, this approach
-introduces searches much more of the commit graph than necessary.
+for gigantic repositories like the Linux kernel, this approach searches
+much more of the commit graph than necessary.
To inspect as little of the graph as possible while still finding recent
commits, I settled on a [breadth-first search][9] which stops after