# HG changeset patch
# User Steve Losh <steve@stevelosh.com>
# Date 1482683646 18000
# Node ID ae7bfb3acac3718b27f9b52198bad98dc642d69b
# Parent  ed3c092a082d168a22c3842d2a70224923994e43# Parent  16bff1faf4ca09a53527d1e772bbf3e7e5243145
Merge.

diff -r ed3c092a082d -r ae7bfb3acac3 content/blog/2009/01/going-open-source.markdown
--- a/content/blog/2009/01/going-open-source.markdown	Sun Dec 25 11:32:24 2016 -0500
+++ b/content/blog/2009/01/going-open-source.markdown	Sun Dec 25 11:34:06 2016 -0500
@@ -75,10 +75,12 @@
 through my code and saw a bug that you wanted to fix, you could do the
 following:
 
-* Clone the repository to your own machine. * Fix the bug in that local copy,
-committing to your local repository as you go. * Go back to the website and
-click the "Pull Request" button. * I review the changes. * If I like them I
-press a button to merge them into the main repository.
+* Clone the repository to your own machine.
+* Fix the bug in that local copy, committing to your local repository as you
+  go.
+* Go back to the website and click the "Pull Request" button.
+* I review the changes.
+* If I like them I press a button to merge them into the main repository.
 
 Once the changes are in the main repository I just run a single script to
 redeploy the site as usual and the changes are live. It's really an almost