From 351155d7a9599fce4bd532106c6baa14f940b0dc Mon Sep 17 00:00:00 2001
From: leithoff <mail@leithoff.net>
Date: Fri, 8 Jul 2016 12:54:20 +0200
Subject: [PATCH] Updated CodeCorner3 (markdown)

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

diff --git a/CodeCorner3.md b/CodeCorner3.md
index b4f5c75..ff4833f 100644
--- a/CodeCorner3.md
+++ b/CodeCorner3.md
@@ -8,7 +8,7 @@ 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>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>Documenttypedefinition (DTD): <pre> &lt;!DOCTYPE overlay PUBLIC "-//Stylite AG//eTemplate 2//EN" "http://www.egroupware.org/etemplate2.dtd"&gt;</pre> 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>eTemplates can be (and are usually) nested, eg. a template-field can contain an other eTemplate </strong></li>