From d8931a832e843c72fa198daa4d747b4362a6e416 Mon Sep 17 00:00:00 2001
From: Holger Reinhardt <holger@launchd.de>
Date: Wed, 3 Feb 2016 14:53:23 +0100
Subject: [PATCH] Kramdown syntax driving me nuts

---
 _posts/2016-01-18-fluentd-log-parsing.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/_posts/2016-01-18-fluentd-log-parsing.md b/_posts/2016-01-18-fluentd-log-parsing.md
index 077467f..98d6fab 100644
--- a/_posts/2016-01-18-fluentd-log-parsing.md
+++ b/_posts/2016-01-18-fluentd-log-parsing.md
@@ -26,7 +26,7 @@ The simplest approach is to just parse all messages using the common denominator
 
 In the case of a typical log file a configuration can be something like this (but not necessarily):
 
- ~~~ xml
+~~~ xml
 <source>
   type tail
   path /var/log/test.log
@@ -38,7 +38,7 @@ In the case of a typical log file a configuration can be something like this (bu
   #a timestamp in front of it, the rest is just stored in the field 'message'
   format1 /(?<time>\d{4}-\d{1,2}-\d{1,2} \d{1,2}:\d{1,2}:\d{1,2},\d{3}) (?<message>(.|\s)*)/
 </source>
- ~~~
+~~~
 
 You will notice we still do a bit of parsing, the minimal level would be to just have a multiline format to split the log contents into separate messages and then to push the contents on.