From e82f7e13130c789c0c72217bd90947947e9d7ff5 Mon Sep 17 00:00:00 2001
From: John Cortell <john.cortell@freescale.com>
Date: Mon, 26 Apr 2010 21:13:35 +0000
Subject: [PATCH] Minor: more useful title for context help I added last week

---
 doc/org.eclipse.cdt.doc.user/contexts_CDT_DEBUGGER_DSFGDB.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/org.eclipse.cdt.doc.user/contexts_CDT_DEBUGGER_DSFGDB.xml b/doc/org.eclipse.cdt.doc.user/contexts_CDT_DEBUGGER_DSFGDB.xml
index fe212089711..f5fe3e23822 100644
--- a/doc/org.eclipse.cdt.doc.user/contexts_CDT_DEBUGGER_DSFGDB.xml
+++ b/doc/org.eclipse.cdt.doc.user/contexts_CDT_DEBUGGER_DSFGDB.xml
@@ -15,7 +15,7 @@
    <description>Control the behavior of the C/C++ debugger when debugging with GDB, specifically when using a GDB (DSF) launcher.</description>
    <topic href="reference/cdt_u_dsfgdb.htm" label="GDB Preferences"/>
 </context>
-<context id="update_threadlist_button_context" title="About this checkbox">
+<context id="update_threadlist_button_context" title="Force thread list update on suspend">
    <description>This checkbox controls whether the CDT debugger will ask gdb for the target program&apos;s thread list on each suspend event (breakpoint-hit, step, etc). Normally, this isn&apos;t necessary, as GDB sends notifications in realtime when a thread is created or destroyed. However, some lightweight GDB remote stubs won&apos;t send these notifications. As such, the CDT debugger doesn&apos;t find out about new or destroyed threads unless it polls gdb. Turn on this option if you are debugging such a target (typically an embedded one).</description>
 </context>