From 532e9b08b7aeb18a94adbbaf75d0a9d043d51fb0 Mon Sep 17 00:00:00 2001 From: Adam Shaw Date: Mon, 26 Aug 2013 22:15:02 -0700 Subject: [PATCH] fix line breaks in readme --- readme.md | 19 +++++-------------- 1 file changed, 5 insertions(+), 14 deletions(-) diff --git a/readme.md b/readme.md index 1c6cc84..6fb9ef5 100644 --- a/readme.md +++ b/readme.md @@ -2,18 +2,13 @@ FullCalendar - Full-sized drag & drop event calendar ==================================================== -This document describes how to modify or contribute to the FullCalendar project. -If you are looking for end-developer documentation, please visit -the [project homepage](http://arshaw.com/fullcalendar/). +This document describes how to modify or contribute to the FullCalendar project. If you are looking for end-developer documentation, please visit the [project homepage](http://arshaw.com/fullcalendar/). Getting Set Up -------------- -You will need [Git](http://git-scm.com/), [Node](http://nodejs.org/), and NPM installed. -For clarification, please view the -[jQuery readme](https://github.com/jquery/jquery/blob/master/README.md#what-you-need-to-build-your-own-jquery), -which requires a similar setup. +You will need [Git](http://git-scm.com/), [Node](http://nodejs.org/), and NPM installed. For clarification, please view the [jQuery readme](https://github.com/jquery/jquery/blob/master/README.md#what-you-need-to-build-your-own-jquery), which requires a similar setup. Also, you will need to have the [Grunt](http://gruntjs.com/) build system installed globally (`-g`) on your system: @@ -31,8 +26,7 @@ Enter the directory and install FullCalendar's development dependencies: Development Workflow -------------------- -After you make code changes, you'll want to compile the JS/CSS so that it can be previewed from the tests and demos. -You can either manually rebuild each time you make a change: +After you make code changes, you'll want to compile the JS/CSS so that it can be previewed from the tests and demos. You can either manually rebuild each time you make a change: grunt dev @@ -42,8 +36,7 @@ Or, you can run a script that automatically rebuilds whenever you save a source You can optionally add the `--sourceMap` flag to output source maps for debugging. -When you are finished, run the following command to write the distributable files into the `./build/out/` -and `./build/dist/` directories: +When you are finished, run the following command to write the distributable files into the `./build/out/` and `./build/dist/` directories: grunt @@ -55,6 +48,4 @@ If you want to clean up the generated files, run: Writing Tests ------------- -When fixing a bug or writing a feature, please make a corresponding HTML file in the `./tests/` directory -to visually demonstrate your work. If the test requires user intervention to prove its point, please write -instructions for the user to follow. Explore the existing tests for more info. \ No newline at end of file +When fixing a bug or writing a feature, please make a corresponding HTML file in the `./tests/` directory to visually demonstrate your work. If the test requires user intervention to prove its point, please write instructions for the user to follow. Explore the existing tests for more info. \ No newline at end of file