Skip to content

Change few links to common style #786

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.

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

Merged
merged 4 commits into from
Feb 27, 2017
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion src/v2/guide/components.md
Original file line number Diff line number Diff line change
Expand Up @@ -1050,7 +1050,7 @@ Vue.component(
)
```

When using [local registration](https://vuejs.org/v2/guide/components.html#Local-Registration), you can also directly provide a function that returns a `Promise`:
When using [local registration](components.html#Local-Registration), you can also directly provide a function that returns a `Promise`:

``` js
new Vue({
Expand Down
2 changes: 1 addition & 1 deletion src/v2/guide/deployment.md
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,7 @@ rollup({

When using in-DOM templates or in-JavaScript template strings, the template-to-render-function compilation is performed on the fly. This is usually fast enough in most cases, but is best avoided if your application is performance-sensitive.

The easiest way to pre-compile templates is using [Single-File Components](./single-file-components.html) - the associated build setups automatically performs pre-compilation for you, so the built code contains the already compiled render functions instead of raw template strings.
The easiest way to pre-compile templates is using [Single-File Components](single-file-components.html) - the associated build setups automatically performs pre-compilation for you, so the built code contains the already compiled render functions instead of raw template strings.

If you are using Webpack, and prefer separating JavaScript and template files, you can use [vue-template-loader](https://github.com/ktsn/vue-template-loader), which also transforms the template files into JavaScript render functions during the build step.

Expand Down
2 changes: 1 addition & 1 deletion src/v2/guide/installation.md
Original file line number Diff line number Diff line change
Expand Up @@ -202,7 +202,7 @@ Apply a global [envify](https://github.com/hughsk/envify) transform to your bund
NODE_ENV=production browserify -g envify -e main.js | uglifyjs -c -m > build.js
```

Also see [Production Deployment Tips](./deployment.html).
Also see [Production Deployment Tips](deployment.html).

### CSP environments

Expand Down
4 changes: 2 additions & 2 deletions src/v2/guide/render-function.md
Original file line number Diff line number Diff line change
Expand Up @@ -360,7 +360,7 @@ on: {

### Slots

You can access static slot contents as Arrays of VNodes from [`this.$slots`](http://vuejs.org/v2/api/#vm-slots):
You can access static slot contents as Arrays of VNodes from [`this.$slots`](../api/#vm-slots):

``` js
render: function (createElement) {
Expand All @@ -369,7 +369,7 @@ render: function (createElement) {
}
```

And access scoped slots as functions that return VNodes from [`this.$scopedSlots`](http://vuejs.org/v2/api/#vm-scopedSlots):
And access scoped slots as functions that return VNodes from [`this.$scopedSlots`](../api/#vm-scopedSlots):

``` js
render: function (createElement) {
Expand Down