--- a/sysperfana/perfinvestigator/com.nokia.carbide.cpp.pi.doc.user/html/reference/profiler/ITT_trace.htm	Tue Apr 20 14:41:43 2010 +0300
+++ b/sysperfana/perfinvestigator/com.nokia.carbide.cpp.pi.doc.user/html/reference/profiler/ITT_trace.htm	Wed Apr 21 15:14:16 2010 +0300
@@ -14,6 +14,6 @@
 <p>When you import a Profiler data file (*.dat) that contains dynamic binary support trace information, the importer needs to locate the compiled dynamic binary files. The importer relies on .pkg, .oby, and .iby files for mapping the fullpath binary names on the target device to the compiled dynamic binaries.</p>
 <p>If you specified a Carbide.c++ project for importing, the associated .pkg file will be automatically added. On the other hand, you may have a .oby or .iby file, such as the ROFS .oby file, that contains a list of binaries to be included. If an oby/iby file is added to the list, the importer automatically leaves out files that are known not to be binary executable data.   If you specified a Carbide.c++ project or EPOCROOT, the importer will try to help you find oby/iby files to add.</p>
 <p>If you have custom files in your oby/iby file that are not binary executables and should not take part in the analysis, you might consider removing them from the oby/iby before continuing with the analysis. If those files are very large, processing might take longer.</p>
-<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
+<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>
 </body>
 </html>
\ No newline at end of file