From 2575b8a597d3febb0088d02fb64214c3dbd5fd57 Mon Sep 17 00:00:00 2001
From: Cameron McEfee <cameron@github.com>
Date: Mon, 16 May 2011 10:23:11 -0700
Subject: bring documentation in line with new styles

---
 _posts/2009-10-05-dealing-with-lineendings.textile | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to '_posts/2009-10-05-dealing-with-lineendings.textile')

diff --git a/_posts/2009-10-05-dealing-with-lineendings.textile b/_posts/2009-10-05-dealing-with-lineendings.textile
index 8e99023..3296e3d 100644
--- a/_posts/2009-10-05-dealing-with-lineendings.textile
+++ b/_posts/2009-10-05-dealing-with-lineendings.textile
@@ -5,9 +5,9 @@ description: How to ensure that line endings are consistent in your repo
 categories: troubleshooting windows mac linux
 ---
 
-Line endings... the scourge of every Windows-based developer that tries to mingle with linux- or mac-based developers.  Though most modern text editors can handle both newline types without issue, git is not as graceful.
+<p class="intro">Line endings... the scourge of every Windows-based developer that tries to mingle with linux- or mac-based developers.  Though most modern text editors can handle both newline types without issue, git is not as graceful.</p>
 
-For more info on the issue see "Wikipedia":http://en.wikipedia.org/wiki/Newline.
+<p class="intro">For more info on the issue see "Wikipedia":http://en.wikipedia.org/wiki/Newline.</p>
 
 h2. Mac and Linux users, you don't get to sit this one out
 
-- 
cgit v1.3.1

