diff --git a/Core-API.md b/Core-API.md
index c77616e..8a20e74 100644
--- a/Core-API.md
+++ b/Core-API.md
@@ -15,7 +15,7 @@ In order to bootstrap the WebSlides you'll need to create a instance of it:
const ws = new WebSlides();
```
-That'll make everything run without any hassle. Note that we're using a convention over configuration here, for WebSlides to actually work you need a container with an `id` of `webslides' and ` Goes to a given slide. Goes to the next slide. Goes to the previous slide. Starts autosliding. Stops autosliding. Goes to the previous slide. Registers a plugin to be loaded when the instance is created. It allows
- (on purpose) to replace default plugins.
- Those being:
-
-
+ (on purpose) to replace default plugins.
number
| Amount of milliseconds to wait to go to next slide automatically. |
-
-
-
-### `stop()`
-Stops autosliding.
-
### `registerPlugin(key, cto)`
@@ -125,20 +101,4 @@ Those being:
| Param | Type | Description |
| --- | --- | --- |
| key | string
| They key under which it'll be stored inside of the instance, inside the plugins dict. |
-| cto | function
| Plugin constructor. |
-
-### Plugin development
-
-Almost every single feature of WebSlides is a plugin that can be overwritten and you are able to create your custom plugins. Just call `registerPlugin` (as seen above) **before creating** the instance:
-
-```javascript
-// Adding the constructor to WebSlides
-WebSlides.registerPlugin('myPlugin', MyPlugin);
-
-// Starting WebSlides
-// Your plugin will be constructed at this time and it will receive the webslides instance as the only parameter.
-const ws = new WebSlides();
-// You can also access ws.plugins.myPlugin now
-```
-
-This allows you to rewrite the navigation to use a menu (for example) or add that missing piece of functionality you'd like to see. See [this part of the code](../src/js/modules/webslides.js#L11) to see all the plugins we're using and the name they're using.
+| cto | function
| Plugin constructor. |
\ No newline at end of file