From 83ea25d92675b87d52330df217e3653a47daa9e1 Mon Sep 17 00:00:00 2001
From: Thorn Walli <thorn.walli@grabarzundpartner.de>
Date: Sun, 2 Feb 2020 02:11:00 +0100
Subject: [PATCH] fix(readme): update readme

---
 README.md | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/README.md b/README.md
index 9ea1a200..78787c9d 100755
--- a/README.md
+++ b/README.md
@@ -107,8 +107,6 @@ yarn add nuxt-custom-elements # or npm install nuxt-custom-elements
 | `staticPath` | `String`          | Path to the `static` directory.                                                                                                               | `null`        | `false`  |
 | `entries`    | `Array`           | Defines the component bundles.<br><br>Components can be distributed in separate end points.<br>Allows the targeted distribution of resources. | `null`        | `true`   |
 
----
-
 ## Entry
 
 ```js
@@ -147,8 +145,6 @@ yarn add nuxt-custom-elements # or npm install nuxt-custom-elements
 | `name` | `String` | Name of the endpoint.<br>Value will be converted to ParamCase later.<br><br>Example: `EndpointName` -> `endpoint-name` |
 | `tags` | `Array`  | Tag of the endpoint.<br>Value will be converted to ParamCase later.                                                    |
 
----
-
 ## Tag
 
 | Name      | Type      | Description                                                                                                                           |
@@ -221,7 +217,6 @@ Or execute a `nuxt build`, the files are located under `.nuxt/nuxt-custom-elemen
 To develop a custom component in dev mode, the endpoint must be called in the create method of a page.
 
 ```html
-
 <script>
 export {
   data () {
@@ -237,7 +232,6 @@ export {
   }
 }
 </script>
-
 ```
 
 The custom elements contained in the page template can now be called.