Skip to content

Commit b5f93e7

Browse files
committed
typos
1 parent 765f2ef commit b5f93e7

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ export default {
3131
}
3232
```
3333

34-
Now import that file in `main.js` and pass it to `vue-extensionpoints`:
34+
Now import that file into `main.js` and pass it to `vue-extensions`:
3535

3636
```javascript
3737

@@ -72,7 +72,7 @@ You have an `<extensionpoint>` tag in your project available now:
7272
</template>
7373
```
7474

75-
The *vue-extensionpoints* plugin renders the hooked elements replacing the <extensionpoint> element, one after another. It's up to you what the plugin is rendering: One plugin can render a simple `<div>` element with an image, the next plugin (same hook!) can render a complicated component with variables, sub-components etc. The `extensionpoint` renders them one after another. You only have to make sure that your components do what they promise: in the sample case above, `FooListElement` should render a \<li\> element - because it will be rendered within an \<ul\> element. But thee are no constraints, you are free to choose.
75+
The *vue-extensions* plugin renders the hooked elements replacing the <extensionpoint> element, one after another. It's up to you what the plugin is rendering: One plugin can render a simple `<div>` element with an image, the next plugin (same hook!) can render a complicated component with variables, sub-components etc. The `extensionpoint` renders them one after another. You only have to make sure that your components do what they promise: in the sample case above, `FooListElement` should render a \<li\> element - because it will be rendered within an \<ul\> element. But there are no constraints, you are free to choose.
7676

7777

7878
## Development

0 commit comments

Comments
 (0)