--- a/verbage.lua	Sun Jul 17 17:40:00 2011 +0000
+++ b/verbage.lua	Thu Aug 25 00:45:31 2011 +0000
@@ -11,7 +11,7 @@
 - rebroadcasting entire boss sections, entire days.  maybe only whisper
 to specific people rather than broadcast.
 
-- signpost a potential boss kill, pipeline loot until the cache clears
+- [DONE] signpost a potential boss kill, pipeline loot until the cache clears
 
 - Being able to drag rows up and down the main loot grid would be awesome.  Coding
 that would be likely to drive me batshiat insane.
@@ -123,6 +123,10 @@
 The first tab on the left side, <Loot>, is where everything goes to and comes
 from.  Looting events and Deadly Boss Mods notifications go to the <Loot> tab; the
 other tabs are all generated from the information in the <Loot> tab.
+
+|cffff335dNote about these Help pages:|r  The category "titles" on the left side
+have their own help text, in addition to the more specific entries in the expanded
+list.  Read those first before expanding the categories or you'll miss stuff.
 ]]
 
 T.basic_loot = [[
@@ -206,8 +210,7 @@
 
 The addon tries to be smart about logging on during a raid (due to a disconnect or
 relog).  If you log in, are already in a raid group, and loot has already been
-stored from tracking, it will re-enable itself automatically.  It will not (as of
-this writing) restore ancillary settings such as the tracking threshold.
+stored from tracking, it will re-enable itself automatically.
 
 The intent of the addon design is that, after the end of a raid, all the generated
 markup text is done, optionally saved (see "Generated Texts - Saved Texts"), and
@@ -298,8 +301,8 @@
 
 The [url] choice defaults to using Wowhead.  If you have the [item] extension
 for your BBcode installed, you can use either of those choices too.  The "by ID"
-variant is good for heroic ToC/ICC items that share names with nonheroic items,
-but is harder to read in the text tab.
+variant is good for heroic raid items that share names with nonheroic items,
+but the raw output is harder to read in the text tab.
 
 You can also specify a custom string.  Formatting is done with these replacements:
 
@@ -334,28 +337,25 @@
 ]]
 
 T.texts_saved = [[
-The contents of the <Forum Markup> and <Attendance> tabs can be saved, so that they
-will not be lost when you use the +Clear> button.
+The contents of the <Forum Markup>, <Attendance>, and other such tabs can be saved,
+so that they will not be lost when you use the +Clear> button.
 
 Do any edits you want to the generated text tabs, then click the +Save Current As...>
 button on the right-hand side.  Enter a short descriptive reminder (for example,
 "thursday hardmodes") in the popup dialog.  The texts will remain in their tabs,
 but clearing loot information will not lose them now.
 
-All saved texts are listed on the right-hand side.  There is no technical limit to
-the number of saved texts, but the graphical display will begin to overflow after
-about half a dozen saved sets.  (And I don't care.)
-
-Clicking a saved text name lets you +Load> or +Delete> that saved set.  The primary
-<Loot> tab is not saved and restored by this process, only the generated texts.
-This also means you cannot +Regenerate> the texts.
+All saved texts are listed on the right-hand side.  Clicking a saved text name
+lets you +Load> or +Delete> that saved set.  The primary <Loot> tab is not saved
+and restored by this process, only the generated texts.  This also means you cannot
++Regenerate> the texts.
 ]]
 
 T.history = [[
 The <History> tab maintains a list of all loot.  It is intended to help answer
 questions such as "When was the last time PlayerX won something?" and "How much stuff
 has PlayerY gotten lately?"  The history tab is, by design, not as configurable
-as the main <Loot> tab; entries cannot be edited, individually deleted, and so forth.
+as the main <Loot> tab; entries cannot be edited and so forth.
 
 Loot history is the only "live" data tab which persists across the +Clear Loot> command.
 For this reason, very little information is stored:  only the recipient, the item,
@@ -398,9 +398,10 @@
 ]]
 
 T.tips = [[
-Shift-clicking an item in the <Loot> display will paste it into an open chat editbox.
+Shift-clicking an item in the <Loot> or <History> display will paste it into an
+open chat editbox.
 
-The |cffff8000[Ouro Loot]|r "legendary item" link displayed at the start of all
+The |cffff8000[Ouro Loot]|r "legendary item" displayed at the start of all
 chat messages is a clickable link.  Clicking opens the main display.  An option
 on the <Options> tab will cause a message to be printed after a boss kill,
 mostly for lazy loot trackers who don't like typing slash commands to open windows.
@@ -421,6 +422,13 @@
 ]]
 
 T.tips_slashies = [[
+If you give an unrecognized argument to the </ouroloot> slash command, it will
+search the tab titles left to right for a title beginning with the same letters as
+the argument, and open the display to that tab.  For example, <"/loot a"> would
+open the <Attendance> tab, and <"/loot ad"> would open the <Advanced> tab.  If
+you had added a theoretical <EQDKP> tab, then <"/loot eq"> would be the fastest
+way to see it.
+
 The </ouroloot> command can take arguments to do things without going through
 the UI.  Parts given in *(angle brackets)* are required, parts in [square brackets]
 are optional:
@@ -449,13 +457,6 @@
 If you use the slash commands to enable tracking or set loot thresholds, you can
 give numbers or common names for the threshold.  For example, "0", "poor", "trash",
 "gray"/"grey" are all the same, "4", "epic", "purple" are the same, and so on.
-
-If you give an unrecognized argument to the </ouroloot> slash command, it will
-search the tab titles left to right for a title beginning with the same letters as
-the argument, and open the display to that tab.  For example, <"/loot a"> would
-open the <Attendance> tab, and <"/loot ad"> would open the <Advanced> tab.  If
-you had added a theoretical <EQDKP> tab, then <"/loot eq"> would be the fastest
-way to see it.
 ]]
 
 T.todo = [[