From 2bd3815b42d3733bf086170277b846285700d697 Mon Sep 17 00:00:00 2001 From: Suriyaa Kudo Date: Sun, 3 Apr 2016 10:25:18 +0200 Subject: [PATCH] Small edits --- .github/CONTRIBUTING.markdown | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/.github/CONTRIBUTING.markdown b/.github/CONTRIBUTING.markdown index e0f278fe..9c3c985d 100644 --- a/.github/CONTRIBUTING.markdown +++ b/.github/CONTRIBUTING.markdown @@ -6,8 +6,8 @@ Hi there! Interested in contributing to Jekyll? We'd love your help. Jekyll is a * If you have a question about using Jekyll, start a discussion on [Jekyll Talk](https://talk.jekyllrb.com). * If you think you've found a bug within a Jekyll plugin, open an issue in that plugin's repository. -* If you think you've found a bug within Jekyll itself, [open an issue](https://github.com/jekyll/jekyll/issues/new) -* More resources are listed on our [Help page](https://jekyllrb.com/help/) +* If you think you've found a bug within Jekyll itself, [open an issue](https://github.com/jekyll/jekyll/issues/new). +* More resources are listed on our [Help page](https://jekyllrb.com/help/). ## Ways to contribute @@ -28,7 +28,7 @@ Whether you're a developer, a designer, or just a Jekyll devotee, there are lots * The more information, the better. Make judicious use of the pull request body. Describe what changes were made, why you made them, and what impact they will have for users. -* Pull request are easy and fun. If this is your first pull request, it may help to [understand GitHub Flow](https://guides.github.com/introduction/flow/) +* Pull request are easy and fun. If this is your first pull request, it may help to [understand GitHub Flow](https://guides.github.com/introduction/flow/). * If you're submitting a code contribution, be sure to read the [code contributions](#code-contributions) section below. @@ -36,7 +36,7 @@ Whether you're a developer, a designer, or just a Jekyll devotee, there are lots Many small changes can be made entirely through the github.com web interface. -1. Navigate to the file within [`jekyll/jekyll`](https://github.com/jekyll/jekyll) that you'd like to edit +1. Navigate to the file within [`jekyll/jekyll`](https://github.com/jekyll/jekyll) that you'd like to edit. 2. Click the pencil icon in the top right corner to edit the file 3. Make your proposed changes 4. Click "Propose file change" @@ -48,8 +48,8 @@ That's it! You'll be automatically subscribed to receive updates as others revie ### Submitting a pull request via Git command line -1. Fork the project by clicking "Fork" in the top right corner of [`jekyll/jekyll`](https://github.com/jekyll/jekyll) -2. Clone the repository lcoally `git clone https://github.com//jekyll` +1. Fork the project by clicking "Fork" in the top right corner of [`jekyll/jekyll`](https://github.com/jekyll/jekyll). +2. Clone the repository lcoally `git clone https://github.com//jekyll`. 3. Create a new, descriptively named branch to contain your change ( `git checkout -b my-awesome-feature` ). 4. Hack away, add tests. Not necessarily in that order. 5. Make sure everything still passes by running `script/cibuild` (see [the tests section](#running-tests-locally) below)