diff --git a/build.gradle b/build.gradle
index 48f6f22d..1d3d3c99 100644
--- a/build.gradle
+++ b/build.gradle
@@ -2,7 +2,7 @@ apply plugin: 'java'
apply plugin: 'maven'
group 'org.iot.dsa'
-version '0.11.0'
+version '0.20.0'
sourceCompatibility = 1.6
targetCompatibility = 1.6
diff --git a/docs/DeveloperGuide.md b/docs/DeveloperGuide.md
index 1d622a1a..b66af8df 100644
--- a/docs/DeveloperGuide.md
+++ b/docs/DeveloperGuide.md
@@ -53,22 +53,22 @@ Nodes are where application specific logic is bound to the link architecture. N
will use various lifecycle callbacks to trigger their logic.
First you must create a root node. It is the hook for the rest of your functionality. The
-convention is to name it RootNode, but make sure it is in a unique package so that multiple links
+convention is to name it MainNode, but make sure it is in a unique package so that multiple links
can be run in the same process.
Then you will probably create additional nodes that will be descendants in the tree rooted by your
root node.
-### Root Node
+### Main Node
All links require a single root node and it must subclass
-[org.iot.dsa.dslink.DSRootNode](https://iot-dsa-v2.github.io/sdk-dslink-java-v2/javadoc/index.html?org/iot/dsa/dslink/DSRootNode.html).
-The convention is to name the class RootNode but the package must be unique from any other
-RootNodes so that multiple links can be run in the same process.
+[org.iot.dsa.dslink.DSMainNode](https://iot-dsa-v2.github.io/sdk-dslink-java-v2/javadoc/index.html?org/iot/dsa/dslink/DSMainNode.html).
+The convention is to name the class MainNode but the package must be unique from any other
+MainNodes so that multiple links can be run in the same process.
When a link launches the first time, the type of the root node is looked up **dslink.json**.
-The config _rootType_ must store the fully qualified class name of the root node. After the first
-launch, the configuration database is serialized and the _rootType_ config will longer have an
+The config _mainType_ must store the fully qualified class name of the root node. After the first
+launch, the configuration database is serialized and the _mainType_ config will longer have an
impact.
### Additional Nodes
diff --git a/docs/javadoc/allclasses-frame.html b/docs/javadoc/allclasses-frame.html
index 9d715b66..3e5d4768 100644
--- a/docs/javadoc/allclasses-frame.html
+++ b/docs/javadoc/allclasses-frame.html
@@ -2,9 +2,9 @@
Large outbound messages that can be broken into smaller ones should check this occasionally
- when writing. The idea is to prevent buffer overflows as well as not have a single message
- hog communication.