diff --git a/docs/getting_started/basics/exposing_components.md b/docs/getting_started/basics/exposing_components.md
index 1d10540..aab82fc 100644
--- a/docs/getting_started/basics/exposing_components.md
+++ b/docs/getting_started/basics/exposing_components.md
@@ -22,7 +22,7 @@ For example:
 
 By enabling this flag, this module will
 
-* receive a module identifier in the form of `https://linkedsoftwaredependencies.org/bundles/npm/my-plugin`;
+* receive a module identifier in the form of `https://linkedsoftwaredependencies.org/bundles/npm/my-plugin`; (`my-plugin` is your package `name`)
 * expose its components if `components/components.jsonld` exists;
 * expose its context if `components/context.json` exists;
 * expose its components and config folder if `components/` or `config/` exist.
@@ -49,6 +49,13 @@ For instance, the `"lsd:module": true` is typically equivalent to:
 If you however want to adapt any of the above default entries,
 you can make use of the more advanced options below.
 
+### Advanced: Using a new plugin
+
+Project A uses components.js but some functionality is missing or lacking. Creating a Library that implements an interface or extends a class from Project A is an easy way to fix it's shortcomings.
+
+To use this new functionality a new config is required. After copying an existing config it's time to add the new class where needed, also add the Library's context to the config file, something like `https://linkedsoftwaredependencies.org/bundles/npm/my-plugin/^1.0.0/components/context.jsonld`.
+Project A needs the new Library as dependency so the new component is found by compenents.js.
+
 ### Advanced: Custom module URL
 
 The URL of your module can be defined using `"lsd:module"`:
diff --git a/docs/getting_started/basics/workflow_ts.md b/docs/getting_started/basics/workflow_ts.md
index fff1ed1..2140e98 100644
--- a/docs/getting_started/basics/workflow_ts.md
+++ b/docs/getting_started/basics/workflow_ts.md
@@ -13,7 +13,7 @@ These will be explained in detail in the following sections.
 
 ### 1. Setup module and component generation
 
-Using the [`componentsjs-generator`](https://raw.githubusercontent.com/LinkedSoftwareDependencies/Components-Generator.js) tool,
+Using the [`componentsjs-generator`](https://github.com/LinkedSoftwareDependencies/Components-Generator.js) tool,
 our declarative components from our TypeScript classes.
 
 **1. Install as a dev dependency**
@@ -62,8 +62,9 @@ Call `componentsjs-generator` as a npm script by adding a `scripts` entry to you
 
 This is only a _recommended_ way of calling `componentsjs-generator`,
 you are free to call it in a different way that better suits your pipeline.
+By default, `componentsjs-generator` will output generated components into the `components/` directory.
 
-Please refer to the README of [`componentsjs-generator`](https://raw.githubusercontent.com/LinkedSoftwareDependencies/Components-Generator.js)
+Please refer to the README of [`componentsjs-generator`](https://github.com/LinkedSoftwareDependencies/Components-Generator.js)
 for more details on how to change the default options of this tool.
 
 **4. _(optional)_ Ignore generated components files**