diff -r 48780e181b38 -r 578be2adaf3e Symbian3/PDK/Source/GUID-AF495E4C-94EA-439E-9C5C-163BAADA644D.dita
--- a/Symbian3/PDK/Source/GUID-AF495E4C-94EA-439E-9C5C-163BAADA644D.dita	Tue Jul 20 12:00:49 2010 +0100
+++ b/Symbian3/PDK/Source/GUID-AF495E4C-94EA-439E-9C5C-163BAADA644D.dita	Fri Aug 13 16:47:46 2010 +0100
@@ -1,27 +1,27 @@
-<?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 id="GUID-AF495E4C-94EA-439E-9C5C-163BAADA644D" xml:lang="en"><title>Handling
-Multiple Simultaneous Privacy Requests</title><shortdesc>This topic describes how to design a Privacy Controller to handle multiple
-simultaneous privacy requests.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
-<p> An important design decision for a licensee in creating a Privacy Controller
-is if it needs to process multiple simultaneous privacy requests when these
-are sent via the <xref href="GUID-E1710E40-B8F5-5CF8-B9FE-698869A1770F.dita">Privacy
-Request API</xref> or the <xref href="GUID-B3000A78-3BE5-5E0A-A718-87BC9BA03726.dita">Network
-Privacy API</xref>. <xref href="GUID-D857413A-D5A1-5F9F-A780-C980A9E0BEE0.dita">Privacy
-Controller</xref> describes the LBS administration setting <xref href="GUID-6D5954C5-3B6A-3BAA-AB75-D1ECE90BAEDB.dita"><apiname>KLbsSettingMaximumExternalLocateRequests</apiname></xref> that
-controls if the LBS subsystem handles multiple simultaneous privacy requests.</p>
-<p> If LBS is configured to support multiple simultaneous requests then the
-licensee Privacy Controller must also be designed to handle them. This means
-that the Privacy Controller must be written to process calls to <codeph>ProcessNetworkLocationRequest()</codeph>, <codeph>ProcessNetworkPositionUpdate()</codeph> and <codeph>ProcessRequestComplete()</codeph> for multiple requests and
-it must track the state of each privacy request (uniquely identified by its
-request ID). </p>
+<?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 id="GUID-AF495E4C-94EA-439E-9C5C-163BAADA644D" xml:lang="en"><title>Handling
+Multiple Simultaneous Privacy Requests</title><shortdesc>This topic describes how to design a Privacy Controller to handle multiple
+simultaneous privacy requests.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
+<p> An important design decision for a licensee in creating a Privacy Controller
+is if it needs to process multiple simultaneous privacy requests when these
+are sent via the <xref href="GUID-E1710E40-B8F5-5CF8-B9FE-698869A1770F.dita">Privacy
+Request API</xref> or the <xref href="GUID-B3000A78-3BE5-5E0A-A718-87BC9BA03726.dita">Network
+Privacy API</xref>. <xref href="GUID-D857413A-D5A1-5F9F-A780-C980A9E0BEE0.dita">Privacy
+Controller</xref> describes the LBS administration setting <xref href="GUID-6D5954C5-3B6A-3BAA-AB75-D1ECE90BAEDB.dita"><apiname>KLbsSettingMaximumExternalLocateRequests</apiname></xref> that
+controls if the LBS subsystem handles multiple simultaneous privacy requests.</p>
+<p> If LBS is configured to support multiple simultaneous requests then the
+licensee Privacy Controller must also be designed to handle them. This means
+that the Privacy Controller must be written to process calls to <codeph>ProcessNetworkLocationRequest()</codeph>, <codeph>ProcessNetworkPositionUpdate()</codeph> and <codeph>ProcessRequestComplete()</codeph> for multiple requests and
+it must track the state of each privacy request (uniquely identified by its
+request ID). </p>
 </conbody></concept>
\ No newline at end of file