Skip to content

Commit 6ad9979

Browse files
jagannathBhatyyx990803
authored andcommitted
docs: fix spelling and grammatical errors (vuejs#9619)
1 parent d123c7e commit 6ad9979

File tree

7 files changed

+16
-16
lines changed

7 files changed

+16
-16
lines changed

.github/CODE_OF_CONDUCT.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
As contributors and maintainers of this project, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.
44

5-
We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, age, or religion.
5+
We are committed to making participation in this project a harassment-free experience for everyone, regardless of the level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, age, or religion.
66

77
Examples of unacceptable behavior by participants include the use of sexual language or imagery, derogatory comments or personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.
88

.github/COMMIT_CONVENTION.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -58,24 +58,24 @@ The **header** is mandatory and the **scope** of the header is optional.
5858

5959
### Revert
6060

61-
If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of the reverted commit. In the body it should say: `This reverts commit <hash>.`, where the hash is the SHA of the commit being reverted.
61+
If the commit reverts a previous commit, it should begin with `revert: `, followed by the header of the reverted commit. In the body, it should say: `This reverts commit <hash>.`, where the hash is the SHA of the commit being reverted.
6262

6363
### Type
6464

65-
If the prefix is `feat`, `fix` or `perf`, it will appear in the changelog. However if there is any [BREAKING CHANGE](#footer), the commit will always appear in the changelog.
65+
If the prefix is `feat`, `fix` or `perf`, it will appear in the changelog. However, if there is any [BREAKING CHANGE](#footer), the commit will always appear in the changelog.
6666

6767
Other prefixes are up to your discretion. Suggested prefixes are `docs`, `chore`, `style`, `refactor`, and `test` for non-changelog related tasks.
6868

6969
### Scope
7070

71-
The scope could be anything specifying place of the commit change. For example `core`, `compiler`, `ssr`, `v-model`, `transition` etc...
71+
The scope could be anything specifying the place of the commit change. For example `core`, `compiler`, `ssr`, `v-model`, `transition` etc...
7272

7373
### Subject
7474

75-
The subject contains succinct description of the change:
75+
The subject contains a succinct description of the change:
7676

7777
* use the imperative, present tense: "change" not "changed" nor "changes"
78-
* don't capitalize first letter
78+
* don't capitalize the first letter
7979
* no dot (.) at the end
8080

8181
### Body

.github/CONTRIBUTING.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -24,13 +24,13 @@ Hi! I'm really excited that you are interested in contributing to Vue.js. Before
2424

2525
- Make sure `npm test` passes. (see [development setup](#development-setup))
2626

27-
- If adding new feature:
27+
- If adding a new feature:
2828
- Add accompanying test case.
29-
- Provide convincing reason to add this feature. Ideally, you should open a suggestion issue first and have it approved before working on it.
29+
- Provide a convincing reason to add this feature. Ideally, you should open a suggestion issue first and have it approved before working on it.
3030

3131
- If fixing bug:
3232
- If you are resolving a special issue, add `(fix #xxxx[,#xxxx])` (#xxxx is the issue id) in your PR title for a better release log, e.g. `update entities encoding/decoding (fix #3899)`.
33-
- Provide detailed description of the bug in the PR. Live demo preferred.
33+
- Provide a detailed description of the bug in the PR. Live demo preferred.
3434
- Add appropriate test coverage if applicable.
3535

3636
## Development Setup
@@ -59,7 +59,7 @@ $ npm run dev:test
5959
# build all dist files, including npm packages
6060
$ npm run build
6161

62-
# run the full test suite, include linting / type checking
62+
# run the full test suite, include linting/type checking
6363
$ npm test
6464
```
6565

@@ -93,7 +93,7 @@ The default test script will do the following: lint with ESLint -> type check wi
9393

9494
- **`core`**: contains universal, platform-agnostic runtime code.
9595

96-
The Vue 2.0 core is platform-agnostic. That is, code inside `core` is able to be run in any JavaScript environment, be it the browser, Node.js, or an embedded JavaScript runtime in native applications.
96+
The Vue 2.0 core is platform-agnostic. That is, the code inside `core` is able to be run in any JavaScript environment, be it the browser, Node.js, or an embedded JavaScript runtime in native applications.
9797

9898
- **`observer`**: contains code related to the reactivity system.
9999

benchmarks/ssr/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
This benchmark renders a table of 1000 rows with 10 columns (10k components), with around 30k normal elements on the page. Note this is not something likely to be seen in a typical app. This benchmark is mostly for stress/regression testing and comparing between `renderToString` and `renderToStream`.
44

5-
To view the results follow the run section. Note that the overall completion time for the results are variable, this is due to other system related variants at run time (available memory, processing power, etc). In ideal circumstances both should finish within similar results.
5+
To view the results follow the run section. Note that the overall completion time for the results is variable, this is due to other system related variants at run time (available memory, processing power, etc). In ideal circumstances, both should finish within similar results.
66

77
`renderToStream` pipes the content through a stream which provides considerable performance benefits (faster time-to-first-byte and non-event-loop-blocking) over `renderToString`. This can be observed through the benchmark.
88

benchmarks/uptime/index.html

+1-1
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@
8282
</div>
8383
<script src="../../dist/vue.min.js"></script>
8484
<script>
85-
// functional components are prefect for small, presentational components
85+
// functional components are perfect for small, presentational components
8686
// and they are much more efficient than stateful ones.
8787
Vue.component('uptime-day', {
8888
props: ['day'],

dist/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@
2525

2626
If you need to compile templates on the fly (e.g. passing a string to the `template` option, or mounting to an element using its in-DOM HTML as the template), you will need the compiler and thus the full build.
2727

28-
When using `vue-loader` or `vueify`, templates inside `*.vue` files are compiled into JavaScript at build time. You don't really need the compiler in the final bundle, and can therefore use the runtime-only build.
28+
When using `vue-loader` or `vueify`, templates inside `*.vue` files are compiled into JavaScript at build time. You don't really need the compiler in the final bundle, and can therefore, use the runtime-only build.
2929

3030
Since the runtime-only builds are roughly 30% lighter-weight than their full-build counterparts, you should use it whenever you can. If you wish to use the full build instead, you need to configure an alias in your bundler.
3131

packages/vue-template-compiler/README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ Note the returned function code uses `with` and thus cannot be used in strict mo
3737
- Type: `boolean`
3838
- Default: `false`
3939

40-
Set this to true will cause the `errors` returned in the compiled result become objects in the form of `{ msg, start, end }`. The `start` and `end` properties are numbers that mark the code range of the error source in the template. This can be passed on to the `compiler.generateCodeFrame` API to generate code frame for the error.
40+
Set this to true will cause the `errors` returned in the compiled result become objects in the form of `{ msg, start, end }`. The `start` and `end` properties are numbers that mark the code range of the error source in the template. This can be passed on to the `compiler.generateCodeFrame` API to generate a code frame for the error.
4141

4242
- `whitespace`
4343
- Type: `string`
@@ -52,7 +52,7 @@ Note the returned function code uses `with` and thus cannot be used in strict mo
5252
If set to `'condense'`:
5353

5454
- A whitespace-only text node between element tags is removed if it contains new lines. Otherwise, it is condensed into a single space.
55-
- Consecutive whitespaces inside a non-whitespace-only text node is condensed into a single space.
55+
- Consecutive whitespaces inside a non-whitespace-only text node are condensed into a single space.
5656

5757
Using condense mode will result in smaller compiled code size and slightly improved performance. However, it will produce minor visual layout differences compared to plain HTML in certain cases.
5858

0 commit comments

Comments
 (0)