From 88bc3e2df32fef7252b01a98c1c9207ade62bf9f Mon Sep 17 00:00:00 2001
From: Rasmus Schultz <mindplay-dk@users.noreply.github.com>
Date: Wed, 16 Dec 2015 16:48:36 +0100
Subject: [PATCH] Mention W3C naming rules as good practice

As established in #2033
---
 src/guide/components.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/guide/components.md b/src/guide/components.md
index e6a866e3cf..728b167a14 100644
--- a/src/guide/components.md
+++ b/src/guide/components.md
@@ -23,6 +23,8 @@ To use this constructor as a component, you need to **register** it with `Vue.co
 Vue.component('my-component', MyComponent)
 ```
 
+Note that Vue.js does not enforce the [W3C rules](http://www.w3.org/TR/custom-elements/#concepts) for custom tag-names (all-lowercase, must contain a hyphen) though following this convention is considered good practice.
+
 Once registered, the component can now be used in a parent instance's template as a custom element, `<my-component>`. Make sure the component is registered **before** you instantiate your root Vue instance. Here's the full example:
 
 ``` html