From 9047b8bdd7f6e5f660b770679ba04ce69206fa2f Mon Sep 17 00:00:00 2001
From: frankiefu <frankiefu@yahoo.com>
Date: Tue, 8 Apr 2014 17:14:36 -0700
Subject: [PATCH] fixup docs and readme

---
 README.md      |  2 +-
 core-meta.html | 95 +++++++++++++++++++++++++-------------------------
 2 files changed, 48 insertions(+), 49 deletions(-)

diff --git a/README.md b/README.md
index c083f07..128d31d 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,4 @@
 core-meta
 =========
 
-See //polymer.github.io/core-meta
\ No newline at end of file
+See the [component page](http://polymer.github.io/core-meta) for more information.
\ No newline at end of file
diff --git a/core-meta.html b/core-meta.html
index ebceb27..2fa826c 100644
--- a/core-meta.html
+++ b/core-meta.html
@@ -6,55 +6,54 @@
 Code distributed by Google as part of the polymer project is also
 subject to an additional IP rights grant found at http://polymer.github.io/PATENTS.txt
 -->
+
 <!--
-/**
- * @group Polymer Core Elements
- *
- * `core-meta` provides a method of constructing a self-organizing database.
- * It is useful to collate element meta-data for things like catalogs and for 
- * designer.
- *
- * Example, an element folder has a `metadata.html` file in it, that contains a 
- * `core-meta`, something like this:
- *
- *     <core-meta id="my-element" label="My Element">
- *       <property name="color" value="blue"></property>
- *     </core-meta>
- *
- * An application can import as many of these files as it wants, and then use 
- * `core-meta` again to access the collected data.
- *
- *     <script>
- *       var meta = document.createElement('core-meta');
- *       console.log(meta.list); // dump a list of all meta-data elements that have been created
- *     </script>
- *
- * Use `byId(id)` to retrive a specific core-meta.
- *
- *     <script>
- *       var meta = document.createElement('core-meta');
- *       console.log(meta.byId('my-element'));
- *     </script>
- *
- * By default all meta-data are stored in a single databse.  If your meta-data 
- * have different types and want them to be stored separately, use `type` to 
- * differentiate them.
- *
- * Example:
- *
- *     <core-meta id="x-foo" type="xElt"></core-meta>
- *     <core-meta id="x-bar" type="xElt"></core-meta>
- *     <core-meta id="y-bar" type="yElt"></core-meta>
- *
- *     <script>
- *       var meta = document.createElement('core-meta');
- *       meta.type = 'xElt';
- *       console.log(meta.list);
- *     </script>
- *
- * @element core-meta
- * @homepage github.io
- */
+
+`core-meta` provides a method of constructing a self-organizing database.
+It is useful to collate element meta-data for things like catalogs and for 
+designer.
+
+Example, an element folder has a `metadata.html` file in it, that contains a 
+`core-meta`, something like this:
+
+    <core-meta id="my-element" label="My Element">
+      <property name="color" value="blue"></property>
+    </core-meta>
+
+An application can import as many of these files as it wants, and then use 
+`core-meta` again to access the collected data.
+
+    <script>
+      var meta = document.createElement('core-meta');
+      console.log(meta.list); // dump a list of all meta-data elements that have been created
+    </script>
+
+Use `byId(id)` to retrive a specific core-meta.
+
+    <script>
+      var meta = document.createElement('core-meta');
+      console.log(meta.byId('my-element'));
+    </script>
+
+By default all meta-data are stored in a single databse.  If your meta-data 
+have different types and want them to be stored separately, use `type` to 
+differentiate them.
+
+Example:
+
+    <core-meta id="x-foo" type="xElt"></core-meta>
+    <core-meta id="x-bar" type="xElt"></core-meta>
+    <core-meta id="y-bar" type="yElt"></core-meta>
+
+    <script>
+      var meta = document.createElement('core-meta');
+      meta.type = 'xElt';
+      console.log(meta.list);
+    </script>
+
+@group Polymer Core Elements
+@element core-meta
+@homepage github.io
 -->
 
 <link rel="import" href="../polymer/polymer.html">