Skip to content

Commit 430a3ad

Browse files
Sherevvkazupon
authored andcommitted
Comments and naming fix (#592)
1 parent c1d35d3 commit 430a3ad

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

Diff for: src/v2/guide/components.md

+4-2
Original file line numberDiff line numberDiff line change
@@ -962,9 +962,11 @@ When registering components (or props), you can use kebab-case, camelCase, or Ti
962962
``` js
963963
// in a component definition
964964
components: {
965-
// register using camelCase
965+
// register using kebab-case
966966
'kebab-cased-component': { /* ... */ },
967+
// register using camelCase
967968
'camelCasedComponent': { /* ... */ },
969+
// register using TitleCase
968970
'TitleCasedComponent': { /* ... */ }
969971
}
970972
```
@@ -978,7 +980,7 @@ Within HTML templates though, you have to use the kebab-case equivalents:
978980
<title-cased-component></title-cased-component>
979981
```
980982

981-
When using _string_ templates however, we're not bound by HTML's case-insensitive restrictions. That means even in the template, you reference your components and props using camelCase, PascalCase, or kebab-case:
983+
When using _string_ templates however, we're not bound by HTML's case-insensitive restrictions. That means even in the template, you reference your components and props using camelCase, TitleCase, or kebab-case:
982984

983985
``` html
984986
<!-- use whatever you want in string templates! -->

0 commit comments

Comments
 (0)