From 51914247d7203f20c68ada9c86031ada7eeba0a7 Mon Sep 17 00:00:00 2001
From: Egor Tensin <Egor.Tensin@gmail.com>
Date: Fri, 30 Jun 2017 19:03:07 +0300
Subject: static-vs: namespace&nbsp;{

---
 _posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to '_posts/2017-06-24-static-vs-inline-vs-unnamed-namespaces.md')

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 24f9287..69bd4f9 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
@@ -1,5 +1,5 @@
 ---
-title: static vs. inline vs. namespace {
+title: static vs. inline vs. namespace&nbsp;{
 layout: post
 excerpt: >
   Should I use <code>static</code>, <code>inline</code> or unnamed namespaces
@@ -154,7 +154,7 @@ name, but are defined in different translation units.
 {: .alert .alert-info }
 
 `namespace {`
--------------
+------------------
 
 With respect to function definitions, unnamed namespaces are, according to my
 understanding, quite similar to the `static` keyword.
-- 
cgit v1.2.3