core/com.nokia.carbide.cpp.doc.user/html/concepts/autotargeting.htm
changeset 2155 fb8db13ce840
parent 2131 ff0156b93599
--- a/core/com.nokia.carbide.cpp.doc.user/html/concepts/autotargeting.htm	Wed Oct 13 14:01:23 2010 -0500
+++ b/core/com.nokia.carbide.cpp.doc.user/html/concepts/autotargeting.htm	Wed Oct 13 14:07:29 2010 -0500
@@ -15,7 +15,7 @@
   <li>The debugger will target any executable not already started whenever a &quot;process load&quot; event occurs, resolving its breakpoints as well.</li>
 </ul>
 <h4>Debugging DLLs</h4>
-<p>One common debugging DLL use case is when the developer doesn't know which process calls the DLL. This makes it difficult to debug the DLL because you doesn't know which process to attach to nor start. Carbide enables DLL debugging  by simply attaching the DLL to any running process as long as the DLL is included in the <a href="../projects/views/view_executables.htm">Executables</a> view. See <a href="../tasks/processes/attach_to_process.htm">Attaching  to a Process</a> for more details.</p>
+<p>One common debugging DLL use case is when the developer doesn't know which process calls the DLL. This makes it difficult to debug the DLL because you don't know which process to attach to or start. Carbide enables DLL debugging  by simply attaching the DLL to any running process as long as the DLL is included in the <a href="../projects/views/view_executables.htm">Executables</a> view. See <a href="../tasks/processes/attach_to_process.htm">Attaching  to a Process</a> for more details.</p>
 <h5>Other References</h5>
 <ul>
   <li><a href="../projects/launch/page_executables.htm">Executables</a></li>