Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Fixed README whitespace in two problematic areas #357

Open
wants to merge 1 commit into from

1 participant

@campadrenalin

Fixed the two spots in the README where the inconsistent whitespace was visible in the Markdown rendering. I could have gone through and normalized everything to spaces, but with the code blocks in <li>s, I figured I'd let sleeping dogs lie, and change things just enough to make it all consistent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
This page is out of date. Refresh to see the latest.
Showing with 2 additions and 2 deletions.
  1. +2 −2 README.mdown
View
4 README.mdown
@@ -84,7 +84,7 @@ in a Github fork, of course.
To initialize a new repo with the basic branch structure, use:
- git flow init [-d]
+ git flow init [-d]
This will then interactively prompt you with some questions on which branches
you would like to use as development and production branches, and how you
@@ -107,7 +107,7 @@ The ``-d`` flag will accept all defaults.
* To push/pull a feature branch to the remote repository, use:
git flow feature publish <name>
- git flow feature pull <remote> <name>
+ git flow feature pull <remote> <name>
* To list/start/finish release branches, use:
Something went wrong with that request. Please try again.