diff --git a/CodeCorner3.md b/CodeCorner3.md
index fa3d0a2..9238827 100644
--- a/CodeCorner3.md
+++ b/CodeCorner3.md
@@ -22,16 +22,11 @@ on day three we went out of base camp eGroupware and stepped into the high field
 	<li>version: VersionNumbers like: '0.8.015'</li>
 	<li>they can have further keys, on loading the class picks the most appropriate one for a user:</li>
 	<li>group: the id of a group if the template is just for that group (that allows admin to show differnt views to each group)</li>
-	<li>template set: they belong too (if the template-set key is empty it is an default-template) they are stored in an array and in serialized form in the db-table 'egw_etemplate'</li>
-	<li>the dialog editor can dump all templates of an app for distribution (so they can be in the CVS too)</li>
-	<li>they encapsulate differnt UI (User Interface) types from the app: at the moment only a HTML one is ready, but a GTK one (using php-gtk, running as native app under linux and win32) and XUL is under development.</li>
+	<li>templates of an app are usually stored for distribution in app/templates/default </li>
 </ul>
 &nbsp;
 
 <h4>how to Setup our application the eGroupware way</h4>
-There is a [http://egroupware.org/egroupware/etemplate/doc/etemplate.html HowTo] for ((eTemplate))s as well and a [http://egroupware.org/egroupware/etemplate/doc/reference.html reference] too.<br />
-The [http://egroupware.org/egroupware/etemplate/doc/etemplate.html HowTo] was helpful to get my first moves with ((eTemplate)) going, but we agreed to rewrite that part at least partially.<br />
-<br />
 Lets consider we want to rebuild our old flagship <tt>test</tt>. Remember the folderstructure?!
 
 <hr style="text-align: left; width: 99%;" />&nbsp;