Skip to content

Commit

Permalink
Cleanup grammar & spelling
Browse files Browse the repository at this point in the history
  • Loading branch information
westim committed Oct 20, 2018
1 parent ba1d87a commit 7a99f15
Showing 1 changed file with 7 additions and 5 deletions.
12 changes: 7 additions & 5 deletions .github/CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Contribution Guide

This document offers a set of guidelines for contributing to VSCodeVim.
These are just guidelines, not rules, use your best judgment and feel free to propose changes to this document.
These are just guidelines, not rules; use your best judgment and feel free to propose changes to this document.
If you need help, drop by on [Slack](https://vscodevim-slackin.azurewebsites.net/).

Thanks for helping us in making VSCodeVim better! :clap:
Expand Down Expand Up @@ -93,14 +93,14 @@ This is my hack to simulate a click event based API in an IDE that doesn't have
To push a release:
```
```bash
gulp release --semver [SEMVER] --githubToken [TOKEN]
git push --follow-tags
```
The above Gulp command will:
1. Bump the package version based off the semver supplied. Supported values: patch, minor, major).
1. Bump the package version based off the semver supplied. Supported values: patch, minor, major.
2. Create a changelog using [github-changelog-generator](https://github.com/github-changelog-generator/github-changelog-generator).
3. Create a Git commit with the above changes.
4. Create a Git tag using the new package version.
Expand All @@ -111,9 +111,11 @@ In addition to building and testing the extension, when a tag is applied to the
### Visual Studio Code Slowdown
If you notice a slowdown and have ever ran `npm test` in the past instread of running tests through VSCode, you might find a `.vscode-test/` folder, which VSCode is continually consuming CPU cycles to index. Long story short, you can speed up VS Code by:
If you notice a slowdown and have ever run `npm test` in the past instead of running tests through VSCode, you might find a `.vscode-test/` folder, which VSCode is continually consuming CPU cycles to index. Long story short, you can speed up VSCode by:
`$ rm -rf .vscode-test/`
```bash
$ rm -rf .vscode-test/
```
## Styleguide
Expand Down

0 comments on commit 7a99f15

Please sign in to comment.