--- a/Symbian3/PDK/Source/GUID-EF3DB813-B0B9-5099-9E57-561A32111BF0.dita	Thu Mar 11 15:24:26 2010 +0000
+++ b/Symbian3/PDK/Source/GUID-EF3DB813-B0B9-5099-9E57-561A32111BF0.dita	Thu Mar 11 18:02:22 2010 +0000
@@ -1,15 +1,15 @@
-<?xml version="1.0" encoding="utf-8"?>
-<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
-<!-- This component and the accompanying materials are made available under the terms of the License 
-"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.
-Contributors: 
--->
-<!DOCTYPE concept
-  PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept xml:lang="en" id="GUID-EF3DB813-B0B9-5099-9E57-561A32111BF0"><title>Feature Manager Server Guide</title><shortdesc>This document describes the feature management server. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody><section><title>Purpose</title> <p>The feature management server maintains the table which contains and maintains the list of features available on the device. </p> </section> <section><title>Required background</title> <p>The feature management system uses the standard client server architecture that is the feature manager server that does the work associated with the feature management functionality. Communication between the application and the server is undertaken by two dlls. </p> </section> <section><title>Architecture</title> <p>The relationship between the parts of the feature management system is : </p> <fig id="GUID-E3DEFD6C-7BA2-5F4B-9771-F6BCF595B3C8"><title>
-             Architecture of the feature management system 
-          </title> <image href="GUID-CE79D1B9-2770-5494-A741-D98DE3EBFA05_d0e560868_href.png" placement="inline"/></fig> </section> <section><title>APIs</title> <p>Communication to and from the feature management server is only provided by the methods available in the <xref href="GUID-40B9136A-B91B-5FF4-A44D-CA6925F19B14.dita#GUID-40B9136A-B91B-5FF4-A44D-CA6925F19B14/GUID-044747C8-90DF-5C93-B0E1-310F283E8894">Feature Manager Client API</xref> and the <xref href="GUID-3FB773BA-C648-5C0A-9022-3F9882C6724A.dita#GUID-3FB773BA-C648-5C0A-9022-3F9882C6724A/GUID-3CF8D502-1181-511C-9F14-A256ACD4EF6B">Feature Manager Discovery API</xref>. </p> </section> <section><title>Typical uses</title> <p>These are the same as for feature management (since it does all the work). They include adding, disabling, enabling and removing features. </p> <p>For the description of the APIs used in feature management look at the component overview for featmgr.dll and featdiscovery.dll. </p> </section> </conbody><related-links><link href="GUID-B71AC5E3-8AA8-55AD-916F-9E873926011B.dita"><linktext>Feature Manager Overview</linktext> </link> <link href="GUID-3FB773BA-C648-5C0A-9022-3F9882C6724A.dita"><linktext>Feature Manager Client
+<?xml version="1.0" encoding="utf-8"?>
+<!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->
+<!-- This component and the accompanying materials are made available under the terms of the License 
+"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.
+Contributors: 
+-->
+<!DOCTYPE concept
+  PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
+<concept xml:lang="en" id="GUID-EF3DB813-B0B9-5099-9E57-561A32111BF0"><title>Feature Manager Server Guide</title><shortdesc>This document describes the feature management server. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody><section><title>Purpose</title> <p>The feature management server maintains the table which contains and maintains the list of features available on the device. </p> </section> <section><title>Required background</title> <p>The feature management system uses the standard client server architecture that is the feature manager server that does the work associated with the feature management functionality. Communication between the application and the server is undertaken by two dlls. </p> </section> <section><title>Architecture</title> <p>The relationship between the parts of the feature management system is : </p> <fig id="GUID-E3DEFD6C-7BA2-5F4B-9771-F6BCF595B3C8"><title>
+             Architecture of the feature management system 
+          </title> <image href="GUID-CE79D1B9-2770-5494-A741-D98DE3EBFA05_d0e560868_href.png" placement="inline"/></fig> </section> <section><title>APIs</title> <p>Communication to and from the feature management server is only provided by the methods available in the <xref href="GUID-40B9136A-B91B-5FF4-A44D-CA6925F19B14.dita#GUID-40B9136A-B91B-5FF4-A44D-CA6925F19B14/GUID-044747C8-90DF-5C93-B0E1-310F283E8894">Feature Manager Client API</xref> and the <xref href="GUID-3FB773BA-C648-5C0A-9022-3F9882C6724A.dita#GUID-3FB773BA-C648-5C0A-9022-3F9882C6724A/GUID-3CF8D502-1181-511C-9F14-A256ACD4EF6B">Feature Manager Discovery API</xref>. </p> </section> <section><title>Typical uses</title> <p>These are the same as for feature management (since it does all the work). They include adding, disabling, enabling and removing features. </p> <p>For the description of the APIs used in feature management look at the component overview for featmgr.dll and featdiscovery.dll. </p> </section> </conbody><related-links><link href="GUID-B71AC5E3-8AA8-55AD-916F-9E873926011B.dita"><linktext>Feature Manager Overview</linktext> </link> <link href="GUID-3FB773BA-C648-5C0A-9022-3F9882C6724A.dita"><linktext>Feature Manager Client
                 Overview</linktext> </link> <link href="GUID-40B9136A-B91B-5FF4-A44D-CA6925F19B14.dita"><linktext>Feature Discovery Overview</linktext> </link> </related-links></concept>
\ No newline at end of file