diff -r 4816d766a08a -r f345bda72bc4 Symbian3/PDK/Source/GUID-546FD573-8136-4C58-878B-C2F643B333AA.dita
--- a/Symbian3/PDK/Source/GUID-546FD573-8136-4C58-878B-C2F643B333AA.dita	Tue Mar 30 11:42:04 2010 +0100
+++ b/Symbian3/PDK/Source/GUID-546FD573-8136-4C58-878B-C2F643B333AA.dita	Tue Mar 30 11:56:28 2010 +0100
@@ -4,15 +4,16 @@
 "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-546FD573-8136-4C58-878B-C2F643B333AA" xml:lang="en"><title>When
-to use dialog architecture</title><prolog><metadata><keywords></keywords></metadata></prolog><conbody>
-<p>One benefit of using dialogs is that the content
-and layout can be changed in resource files, without
-rebuilding any C++ code.</p>
-<p>Avkon has automatic status pane tab handling built into its multipage
-dialogs. This contrasts with the traditional and view architectures,
-for which the application must drive the tabs, that is, implement code for
-switching tabs and updating the navigation pane. </p>
+-->
+<!DOCTYPE concept
+  PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<concept id="GUID-546FD573-8136-4C58-878B-C2F643B333AA" xml:lang="en"><title>When
+to use dialog architecture</title><prolog><metadata><keywords/></metadata></prolog><conbody>
+<p>One benefit of using <xref format="html" href="specs/guides/Dialogs_API_Specification/Dialogs_API_Specification.html" scope="peer">dialogs</xref> is that the content and layout can be changed
+in <xref format="html" href="specs/guides/Dialogs_API_Specification/Dialogs_API_Specification.html#Dialogs_API_Specification.topic3.1" scope="peer">resource</xref> files, without rebuilding any C++ code.</p>
+<p>AVKON has automatic status pane tab handling built into its <xref format="html" href="specs/guides/Dialogs_API_Specification/Dialogs_API_Specification.html#Dialogs_API_Specification.topic3.1.5" scope="peer">Multipage dialogs</xref>. This contrasts with the traditional
+and view architectures, for which the application must drive the tabs, that
+is, implement code for switching tabs and updating the navigation pane. </p>
 </conbody></concept>
\ No newline at end of file