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-05-05-graceful-handling-of-sigint-when-using-pythons-multiprocessingprocess.md b/source/blog/2015-05-05-graceful-handling-of-sigint-when-using-pythons-multiprocessingprocess.md
index 6e0ca9b0..c5f1c915 100644
--- a/source/blog/2015-05-05-graceful-handling-of-sigint-when-using-pythons-multiprocessingprocess.md
+++ b/source/blog/2015-05-05-graceful-handling-of-sigint-when-using-pythons-multiprocessingprocess.md
@@ -2,7 +2,8 @@
 title: "Graceful handling of <code>SIGINT</code> when using Python's <code>multiprocessing.Process</code>"
 date: 2015-05-05T22:03:39-07:00
 date_display: May 5, 2015
----
+...
+
 Today I learned something about Python's (at least CPython's) multiprocessing and signal handling, and I would like to share it here. Basically my situation was such (when developing [`pydoc`](https://github.com/zmwangx/zmwangx.github.io/blob/source/pyblog) that powers this blog):
 
 * I would like to serve the blog with an HTTP server while auto-regenerating for changes;