Change some Markdown to fit other md files' format.

Signed-off-by: Hirohisa Kawase <hiro@linux-eejv.(none)>

laravel/documentation/contrib/command-line.md

@@ -1,28 +1,29 @@
 # Contributing to Laravel via Command-Line
 
 ## Contents
- - [Getting Started](#getting-started)
- - [Forking Laravel](#forking-laravel)
- - [Cloning Laravel](#cloning-laravel)
- - [Adding your Fork](#adding-your-fork)
- - [Creating Branches](#creating-branches)
- - [Committing](#committing)
- - [Submitting a Pull Request](#submitting-a-pull-request)
- - [What's Next?](#whats-next)
 
-<a name='getting-started'></a>
+- [Getting Started](#getting-started)
+- [Forking Laravel](#forking-laravel)
+- [Cloning Laravel](#cloning-laravel)
+- [Adding your Fork](#adding-your-fork)
+- [Creating Branches](#creating-branches)
+- [Committing](#committing)
+- [Submitting a Pull Request](#submitting-a-pull-request)
+- [What's Next?](#whats-next)
+
+<a name="getting-started"></a>
 ## Getting Started
 
 This tutorial explains the basics of contributing to a project on [GitHub](https://github.com/) via the command-line. The workflow can apply to most projects on GitHub, but in this case, we will be focused on the [Laravel](https://github.com/laravel/laravel) project. This tutorial is applicable to OSX, Linux and Windows.
 
 This tutorial assumes you have installed [Git](http://git-scm.com/) and you have created a [GitHub account](https://github.com/signup/free). If you haven't already, look at the [Laravel on GitHub](/docs/contrib/github) documentation in order to familiarize yourself with Laravel's repositories and branches.
 
-<a name='forking-laravel'></a>
+<a name="forking-laravel"></a>
 ## Forking Laravel
 
 Login to GitHub and visit the [Laravel Repository](https://github.com/laravel/laravel). Click on the **Fork** button. This will create your own fork of Laravel in your own GitHub account. Your Laravel fork will be located at **https://github.com/username/laravel** (your GitHub username will be used in place of *username*).
 
-<a name='cloning-laravel'></a>
+<a name="cloning-laravel"></a>
 ## Cloning Laravel
 
 Open up the command-line or terminal and make a new directory where you can make development changes to Laravel:
@@ -36,7 +37,7 @@ Next, clone the Laravel repository (not your fork you made):
 
 > **Note**: The reason you are cloning the original Laravel repository (and not the fork you made) is so you can always pull down the most recent changes from the Laravel repository to your local repository.
 
-<a name='adding-your-fork'></a>
+<a name="adding-your-fork"></a>
 ## Adding your Fork
 
 Next, it's time to add the fork you made as a **remote repository**:
@@ -49,7 +50,7 @@ Remember to replace *username** with your GitHub username. *This is case-sensiti
 
 Now you have a pristine clone of the Laravel repository along with your fork as a remote repository. You are ready to begin branching for new features or fixing bugs.
 
-<a name='creating-branches'></a>
+<a name="creating-branches"></a>
 ## Creating Branches
 
 First, make sure you are working in the **develop** branch. If you submit changes to the **master** branch, it is unlikely they will be pulled in anytime in the near future. For more information on this, read the documentation for [Laravel on GitHub](/docs/contrib/github). To switch to the develop branch:
@@ -76,7 +77,7 @@ Or if there is a new feature to add or change to the documentation that you want
 
 Now that you have created your own branch and have switched to it, it's time to make your changes to the code. Add your new feature or fix that bug.
 
-<a name='committing'></a>
+<a name="committing"></a>
 ## Committing
 
 Now that you have finished coding and testing your changes, it's time to commit them to your local repository. First, add the files that you changed/added:
@@ -87,10 +88,10 @@ Next, commit the changes to the repository:
 
 	# git commit -s -m "I added some more stuff to the Localization documentation."
 
- - **-s** means that you are signing-off on your commit with your name. This tells the Laravel team know that you personally agree to your code being added to the Laravel core.
- - **-m** is the message that goes with your commit. Provide a brief explanation of what you added or changed.
+"- **-s** means that you are signing-off on your commit with your name. This tells the Laravel team know that you personally agree to your code being added to the Laravel core.
+"- **-m** is the message that goes with your commit. Provide a brief explanation of what you added or changed.
 
-<a name='pushing-to-your-fork'></a>
+<a name="pushing-to-your-fork"></a>
 ## Pushing to your Fork
 
 Now that your local repository has your committed changes, it's time to push (or sync) your new branch to your fork that is hosted in GitHub:
@@ -99,19 +100,19 @@ Now that your local repository has your committed changes, it's time to push (or
 
 Your branch has been successfully pushed to your fork on GitHub.
 
-<a name='submitting-a-pull-request'></a>
+<a name="submitting-a-pull-request"></a>
 ## Submitting a Pull Request
 
 The final step is to submit a pull request to the Laravel repository. This means that you are requesting that the Laravel team pull and merge your changes to the Laravel core. In your browser, visit your Laravel fork at [https://github.com/username/laravel](https://github.com/username/laravel). Click on **Pull Request**. Next, make sure you choose the proper base and head repositories and branches:
 
- - **base repo:** laravel/laravel
- - **base branch:** develop
- - **head repo:** username/laravel
- - **head branch:** feature/localization-docs
+- **base repo:** laravel/laravel
+- **base branch:** develop
+- **head repo:** username/laravel
+- **head branch:** feature/localization-docs
 
 Use the form to write a more detailed description of the changes you made and why you made them. Finally, click **Send pull request**. That's it! The changes you made have been submitted to the Laravel team.
 
-<a name='whats-next'></a>
+<a name="whats-next"></a>
 ## What's Next?
 
 Do you have another feature you want to add or another bug you need to fix? First, make sure you always base your new branch off of the develop branch: