Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README punctuation lines 34, 55, 60 and 62 #504

Merged
merged 1 commit into from
Sep 24, 2014
Merged

Update README punctuation lines 34, 55, 60 and 62 #504

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 4 additions & 6 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ cd dustjs
npm install -g grunt-cli
```

### Fetch all the node dependencies
### Fetch all node dependencies
```
npm install
```
Expand All @@ -52,13 +52,11 @@ grunt test

* Use `grunt dev` while developing\debugging.
This task will start a server and serve Jasmine spec runner on http://localhost:3000/_SpecRunner.html.
This tasks uses unminified dust-full.js so it allows you to easily step through the code in a browser.
This task uses unminified dust-full.js so it allows you to easily step through the code in a browser.

* Use `grunt testClient` to test production version of code (dust-full.min.js) in a browser.
Similarly to `grunt dev` it serves Jasmine spec runner on `http://localhost:3000/_SpecRunner.html`.

* Add unit tests
Unit tests can be found in the `test/jasmine-tests/spec` directory. Help us keep up good test coverage! To view coverage report run `grunt coverage` and open `tmp/coverage/index.html` in a browser.
* Add unit tests. Unit tests can be found in the `test/jasmine-tests/spec` directory. Help us keep up good test coverage! To view coverage report run `grunt coverage` and open `tmp/coverage/index.html` in a browser.

* Add an issue and send a pull request
Pull requests are easier to track if you also include an issue. Sending a pull request from a branch makes it easier for you to resolve conflicts in master
* Add an issue and send a pull request. Pull requests are easier to track if you also include an issue. Sending a pull request from a branch makes it easier for you to resolve conflicts in master