From db4dc708df62fbd33713d4a9e20316608046bf1b Mon Sep 17 00:00:00 2001
From: Sherevv <sherevv@gmail.com>
Date: Fri, 18 Nov 2016 14:51:00 +0400
Subject: [PATCH] Comments and naming fix

---
 src/v2/guide/components.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/src/v2/guide/components.md b/src/v2/guide/components.md
index 3fbb3f8cbe..9e0758b35f 100644
--- a/src/v2/guide/components.md
+++ b/src/v2/guide/components.md
@@ -962,9 +962,11 @@ When registering components (or props), you can use kebab-case, camelCase, or Ti
 ``` js
 // in a component definition
 components: {
-  // register using camelCase
+  // register using kebab-case
   'kebab-cased-component': { /* ... */ },
+  // register using camelCase
   'camelCasedComponent': { /* ... */ },
+  // register using TitleCase
   'TitleCasedComponent': { /* ... */ }
 }
 ```
@@ -978,7 +980,7 @@ Within HTML templates though, you have to use the kebab-case equivalents:
 <title-cased-component></title-cased-component>
 ```
 
-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:
+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:
 
 ``` html
 <!-- use whatever you want in string templates! -->