GP-5265: Move schedule display from Threads to Listing tabs

GhidraDocs/GhidraClass/Debugger/B2-Emulation.html

@@ -238,16 +238,16 @@ snapshot, Ghidra will read that variable from the live target, capture
 it, and provide its value to the emulator.</p>
 <section id="stepping-schedules" class="level3">
 <h3>Stepping Schedules</h3>
-<p>If you had not noticed before, the subtitle of the Threads window
-gives the current snapshot number. If you have stepped in the emulator,
-it will also contain the sequence of steps emulated. Recall the
-<em>time</em> element of the Debugger’s <em>coordinates</em>. (See the
-<a href="A5-Navigation.html">Navigation</a> module if you need a
+<p>If you had not noticed before, the trace tabs include the current
+snapshot number. If you have stepped in the emulator, it will also
+contain the sequence of steps emulated. Recall the <em>time</em> element
+of the Debugger’s <em>coordinates</em>. (See the <a
+href="A5-Navigation.html">Navigation</a> module if you need a
 refresher.) The time element, called the <em>schedule</em>, consists of
-both the current snapshot and the sequence of steps to emulate. The
-subtitle displays that schedule. If you have done any patching of the
-emulator’s state, you may notice some more complicated “steps” in the
-schedule. The syntax is:</p>
+both the current snapshot and the sequence of steps to emulate. The tab
+displays that schedule. If you have done any patching of the emulator’s
+state, you may notice some more complicated “steps” in the schedule. The
+syntax is:</p>
 <ul>
 <li><em>Schedule</em> → <em>Snapshot</em> [ <code>:</code> [
 <em>Step</em> ( <code>;</code> <em>Step</em> ) * ] [ <code>.</code>

GhidraDocs/GhidraClass/Debugger/B2-Emulation.md

@@ -73,12 +73,12 @@ If the emulated target reads a variable that Ghidra has not yet captured into th
 
 ### Stepping Schedules
 
-If you had not noticed before, the subtitle of the Threads window gives the current snapshot number.
+If you had not noticed before, the trace tabs include the current snapshot number.
 If you have stepped in the emulator, it will also contain the sequence of steps emulated.
 Recall the *time* element of the Debugger's *coordinates*.
 (See the [Navigation](A5-Navigation.md) module if you need a refresher.)
 The time element, called the *schedule*, consists of both the current snapshot and the sequence of steps to emulate.
-The subtitle displays that schedule.
+The tab displays that schedule.
 If you have done any patching of the emulator's state, you may notice some more complicated "steps" in the schedule.
 The syntax is: