Corrections and examples

TODO.txt

@@ -4,9 +4,5 @@ why it inherits nx.Observable
 
 Data processors: 003-05 (circle DP left)
 Layouts - 003-06 (describe the built-in ones)
-extended nodes s006-04: example from PCE-OF
 
-create codepens for articles in 003
-
-for events (005)
-don’t forget to register events (before this.fire)
+create codepens for articles in 003

tutorials/tutorial-003-01.md

@@ -53,9 +53,6 @@ See the full example on [Codepen]().
 
 In the detailed example, take a look at "nodeSetConfig" please. That's how we set the label for the nodeset. By default the label is empty.
 
-## Expanded by Default
-TBD: found a bug
-
 ## Important to Know
 That's important to know that:
 
@@ -64,4 +61,6 @@ That's important to know that:
 
 
 ## What's next?
-TBD
+The next topic will be *layers*. It is essential to know what they are designed for and what's the way to efficiently utilize them.
+
+[Read NEXT](./tutorial-003-02.md)

tutorials/tutorial-003-03.md

@@ -108,6 +108,8 @@ pathLayer.removePath(pathInst);
 ## Demo
 ![](../images/tutorial-003-04/topology-path.png)
 
+See example on [Codepen](http://codepen.io/NEXTSUPPORT/pen/dpkjLY?editors=0010#0)
+
 ## What's next?
 The next tutorial will lead you through grouping of nodes.
 

tutorials/tutorial-003-06.md

@@ -7,21 +7,29 @@ Just like data processors, there are a number of built-in layouts that provide y
 These are layouts NeXt is served with. We do recommend you to familiarize youself with them, as you will no longer need to create 
 
 ### Enterprise Network
-
+TBD
 
 ### Hierarchical Layout
+TBD
 
 ### NeXt Force
+TBD
 
 ### US Map
-Here's how it looks like.
+US Map layout depicts the USA outline and provides geographic coordinate system (*latitude* and *longitude*) instead of a normal Cartesian system (with *x-* and *y-* axes). That prevents a developer from translating the geographic coordinates into [x;y] location, which requires some effort. However, access to them remains.
+
+#### US Map: demo
+Here's how it might look like.
 
 ![](../images/tutorial-003-06/usmap.png)
 
 ### World Map
-The distributed version of NeXt does not contain the World Map layout anymore, because it slows the app's performance down.
+The distributive version of NeXt does not contain the World Map layout anymore, because it slows down the application's performance.
 
 ## Create Your Layout
-### Create Map Layout
+TBD
+
+## What's next?
+The following tutorial has a big practial application. It tells you about *scene*, which will give you access to many topology events.
 
-### Create Simple Layout
+[Read NEXT](./tutorial-003-07.mds)

tutorials/tutorial-005.md

@@ -53,6 +53,10 @@ In that case, the second parameter of the callback function will take the messag
 
 [Codepen](http://codepen.io/NEXTSUPPORT/pen/OXZLZr)
 
+Also, see the example of using the events across a class:
+
+[Codepen](http://codepen.io/NEXTSUPPORT/pen/ALbdNb)
+
 ## Watchers
 A watcher is a type of event listener that tracks any change of variable's value.
 

tutorials/tutorial-006-04.md

@@ -44,7 +44,9 @@ Imagine, you want to adhere a tiny icon to each node, that would represent the s
 
 Since the example above is a really brief one, take a look at real code:
 
-Examples: TBD
+[PCE-OF topology configuration](https://github.com/CiscoDevNet/pceof-gui/blob/0ce039a06aef5031454f3948bd99baea2a8b4eb4/gui/src/main/webapp/src/app/components/topology/next_topology.directive.js#L118) on GitHub. The [entire app](https://github.com/CiscoDevNet/pceof-gui) is really cool and worth seeing.
+
+We are also going to exercise this skill in [a practial lesson](./tutorial-007-05.md). 
 
 ## What's Next?
 The next tutorial gives you a brief overview of implemented in NeXt "Model-View-ViewModel" concept.