--- a/Symbian3/PDK/Source/GUID-DD88DD7B-E246-4BF2-B537-5C677728CC49.dita	Tue Mar 30 11:42:04 2010 +0100
+++ b/Symbian3/PDK/Source/GUID-DD88DD7B-E246-4BF2-B537-5C677728CC49.dita	Tue Mar 30 11:56:28 2010 +0100
@@ -4,14 +4,17 @@
 "Eclipse Public License v1.0" which accompanies this distribution, 
 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->
 <!-- Initial Contributors:
-	Nokia Corporation - initial contribution.
+    Nokia Corporation - initial contribution.
 Contributors: 
--->  <!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"><concept id="GUID-DD88DD7B-E246-4BF2-B537-5C677728CC49" xml:lang="en"><title>Dialog
-architecture</title><prolog><metadata><keywords></keywords></metadata></prolog><conbody>
+-->
+<!DOCTYPE concept
+  PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<concept id="GUID-DD88DD7B-E246-4BF2-B537-5C677728CC49" xml:lang="en"><title>Dialog
+architecture</title><prolog><metadata><keywords/></metadata></prolog><conbody>
 <p>Dialog architecture refers to a case where the dominant model for views
-in the application is that of dialogs. One particular
-case example of this is when the main view is run as a dialog. Multipage dialogs can
-be used to give a set of views in conformance with the Symbian UI concept.</p>
+in the application is that of <xref format="html" href="specs/guides/Dialogs_API_Specification/Dialogs_API_Specification.html" scope="peer">dialogs</xref>. One particular case example of this is when the
+main view is run as a <xref format="html" href="specs/guides/Dialogs_API_Specification/Dialogs_API_Specification.html" scope="peer">dialogs</xref>. <xref format="html" href="specs/guides/Dialogs_API_Specification/Dialogs_API_Specification.html#Dialogs_API_Specification.topic3.1.5" scope="peer">Multipage dialogs</xref> can be used to give a set of views in
+conformance with the Symbian UI concept.</p>
 <note>
 <p>Nested dialogs can use quite a lot of stack space if not written carefully.</p>
 </note>