summaryrefslogtreecommitdiff
path: root/_posts/2010-01-16-deploy-keys.markdown
diff options
context:
space:
mode:
authorCameron McEfee <cameron@github.com>2011-05-16 14:07:48 -0700
committerCameron McEfee <cameron@github.com>2011-05-16 16:55:31 -0700
commita483a05335c753555aba8c4529a62eb50b470028 (patch)
tree13309e7ff7b36f6020390e19067ff2251e26456d /_posts/2010-01-16-deploy-keys.markdown
parentb9e8a41be8370615b233e01da697d1e6cba0b3f6 (diff)
Update files to match new style guide
Diffstat (limited to '_posts/2010-01-16-deploy-keys.markdown')
-rw-r--r--_posts/2010-01-16-deploy-keys.markdown2
1 files changed, 1 insertions, 1 deletions
diff --git a/_posts/2010-01-16-deploy-keys.markdown b/_posts/2010-01-16-deploy-keys.markdown
index c68cff6..6f5bc4f 100644
--- a/_posts/2010-01-16-deploy-keys.markdown
+++ b/_posts/2010-01-16-deploy-keys.markdown
@@ -5,7 +5,7 @@ description: Do you need a deploy key?
categories: deploying
---
-Deploy keys are a handy yet misunderstood feature here on github. This guide will explain when and how to use them instead of normal user keys.
+<p class="intro">Deploy keys are a handy yet misunderstood feature here on github. This guide will explain when and how to use them instead of normal user keys.</p>
##Do you even need a deploy key?