From a483a05335c753555aba8c4529a62eb50b470028 Mon Sep 17 00:00:00 2001
From: Cameron McEfee <cameron@github.com>
Date: Mon, 16 May 2011 14:07:48 -0700
Subject: Update files to match new style guide

---
 _posts/2010-01-29-rebase.markdown | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to '_posts/2010-01-29-rebase.markdown')

diff --git a/_posts/2010-01-29-rebase.markdown b/_posts/2010-01-29-rebase.markdown
index 8fce0f6..40539cf 100644
--- a/_posts/2010-01-29-rebase.markdown
+++ b/_posts/2010-01-29-rebase.markdown
@@ -5,7 +5,7 @@ description: Using git rebase to restructure a branch
 categories: everyday_git
 ---
 
-One often overlooked feature of git is the `git rebase` command.  Rebase allows you to easily change a series of commits, reordering, editing, or squashing commits together into a single commit.
+<p class="intro">One often overlooked feature of git is the <code>git rebase</code> command. Rebase allows you to easily change a series of commits, reordering, editing, or squashing commits together into a single commit.</p>
 
 <span class="attention">It is considered bad practice to rebase commits which you have already pushed to a remote repo.  Doing so may invoke the wrath of the git gods... you have been warned.</span>
 
-- 
cgit v1.3.1