From 098b08c106b146a339bed7bbb55c6b3bdc0d38da Mon Sep 17 00:00:00 2001
From: Egor Tensin <Egor.Tensin@gmail.com>
Date: Sun, 18 Feb 2018 05:59:12 +0300
Subject: markdownify post excerpts

---
 _posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md | 4 ++--
 _posts/2018-02-18-peculiar-indentation.md                   | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

(limited to '_posts')

diff --git a/_posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md b/_posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md
index 6f9f3dc..94b5105 100644
--- a/_posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md
+++ b/_posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md
@@ -2,8 +2,8 @@
 title: static vs. inline vs. namespace&nbsp;{
 layout: post
 excerpt: >
-  Should I use <code>static</code>, <code>inline</code> or unnamed namespaces
-  for function definitions?
+  Should I use `static`, `inline` or unnamed namespaces for function
+  definitions?
 category: C++
 custom_css:
   - snippets.css
diff --git a/_posts/2018-02-18-peculiar-indentation.md b/_posts/2018-02-18-peculiar-indentation.md
index fceba33..6ec7c73 100644
--- a/_posts/2018-02-18-peculiar-indentation.md
+++ b/_posts/2018-02-18-peculiar-indentation.md
@@ -2,8 +2,8 @@
 title: Peculiar Haskell indentation
 layout: post
 excerpt: >
-  An explanation for nasty <code>parse error</code>s I used to get for nested
-  <code>do</code> blocks.
+  An explanation for nasty `parse error`s I used to get for nested `do`
+  blocks.
 category: Haskell
 custom_css:
   - syntax.css
-- 
cgit v1.2.3