Skip to content

Commit

Permalink
Fix a small typo in documentation (#96)
Browse files Browse the repository at this point in the history
  • Loading branch information
mysticmind authored and LinusBorg committed Jan 2, 2018
1 parent 081b93a commit dccd260
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,7 @@ The order the content is rendered in can be adjusted through the `order` prop on

### Removing the Wrapper element

Vue components always need a single root element. Since `<portal-target>` can't know in advance weither or not it will receive content with more than one root element, it will ender a wrapper element around the content to provide a single root node.
Vue components always need a single root element. Since `<portal-target>` can't know in advance weither or not it will receive content with more than one root element, it will render a wrapper element around the content to provide a single root node.

However, if you know that you will send content with a single root element only, you can use the `slim` prop to tell `<portal-target>` to render that element only and do without the wrapper element.

Expand Down Expand Up @@ -259,7 +259,7 @@ Now you can position your components with `position: absolute` instead

If you use Vue for small bits and pieces on your website, but want to render something in a location at the other end of the page, PortalVue got you covered.

### Tell us about your usecase!
### Tell us about your use case!

We're sure you will find use cases beyond the ones we mentioned. If you do, please
let us know by opening an issue on <a href="http://github.com/linusborg/portal-vue">Github</a>
Expand Down

0 comments on commit dccd260

Please sign in to comment.