Markdown source files: Use ... to end YAML metadata block

Also add a newline after the metadata block.

... is easier on markdown-mode; if --- is used, the line immediately
above it will be treated as a setext header and highlighted, which isn't
so easy on the eyes.

1 files changed, 2 insertions, 1 deletions

diff --git a/source/blog/2015-08-05-switching-to-capitalized-commit-messages.md b/source/blog/2015-08-05-switching-to-capitalized-commit-messages.md
index 04a018f5..f5815d41 100644
--- a/source/blog/2015-08-05-switching-to-capitalized-commit-messages.md
+++ b/source/blog/2015-08-05-switching-to-capitalized-commit-messages.md
@@ -2,7 +2,8 @@
 title: "Switching to capitalized commit messages"
 date: 2015-08-05T19:38:37-07:00
 date_display: August 5, 2015
----
+...
+
 This post is a note to self.
 
 As a long time git user, I've always used lowercase commit messages (in the subject line). I never quite liked the idea of capitalized commit messages, which are seldom complete sentences (and they are never period-terminated). Similarly, I avoid capilatization like hell in comments, unless when I write complete sentences. By the way, there's a technical advantage of writing lowercase commit messages: I can easily tell my human-made commits from auto commits like merge and revert commits, because they always begin with a capitalized "Merge", "Revert", etc.