From 30c35d68758bc4935cc89be75fd479c32a118687 Mon Sep 17 00:00:00 2001
From: leithoff <mail@leithoff.net>
Date: Thu, 7 Jul 2016 16:01:07 +0200
Subject: [PATCH] Updated CodeCorner3 (markdown)

---
 CodeCorner3.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/CodeCorner3.md b/CodeCorner3.md
index b635404..fa3d0a2 100644
--- a/CodeCorner3.md
+++ b/CodeCorner3.md
@@ -8,10 +8,9 @@ on day three we went out of base camp eGroupware and stepped into the high field
 <ul>
 	<li>splitting design and layout</li>
 	<li>there is no EGroupware specific dialog-editor (one part of the etemplate-app) to create the eTemplate<strong> but </strong> a EGroupware specific DTD. So any XML-Capable Editor will do.</li>
-<li>&lt;!DOCTYPE overlay PUBLIC "-//Stylite AG//eTemplate 2//EN" "http://www.egroupware.org/etemplate2.dtd"&gt;</li>
+<li>Documenttypedefinition (DTD): &lt;!DOCTYPE overlay PUBLIC "-//Stylite AG//eTemplate 2//EN" "http://www.egroupware.org/etemplate2.dtd"&gt; Always add that to your .xet files</li>
 	<li><strong>XSS security</strong></li>
 	<li><strong>no parsing of $_POST needed</strong></li>
-	<li><strong>no HTML knowledge needed</strong></li>
 	<li><strong>eTemplates can be (and are usually) nested, eg. a template-field can contain an other eTemplate </strong></li>
 	<li><strong>language independent interfacing:</strong> each field / cell of the template can have a label which is automaticaly run through lang() (the content of the field can be run through lang() too)
 	<ul>