--- a/verbage.lua	Sat May 12 11:08:23 2012 +0000
+++ b/verbage.lua	Tue May 29 22:50:09 2012 +0000
@@ -4,7 +4,7 @@
 
 - implement ack, then fallback to recording if not ack'd
 
-- special treatment for recipes / BoE items?  default to guild vault?
+- special treatment for recipes / BoE items?  default to guild vault?  (DONE for user-configurable list of items defaulting to crafting drops)
 
 - [DONE,TEST,comm] rebroadcasting entire boss sections, entire days.  (TODO: maybe only whisper
 to specific people rather than broadcast.)
@@ -81,6 +81,10 @@
 				value = "slashies",
 				text = "Slash Commands",
 			},
+			{
+				value = "prescan",
+				text = "Prescanning",
+			},
 		},
 	},
 	{
@@ -103,7 +107,10 @@
 -- paragraphs.  This file needs to be edited with a text editor that doesn't
 -- do anything stupid by placing extra spaces at the end of lines.
 do
-local replacement_colors = { ["+"]="|cff30adff", ["<"]="|cff00ff00", [">"]="|r" }
+local replacement_colors = {
+	["+"]="|cff30adff", -- blue: right-click options, control panel names
+	["<"]="|cff00ff00", -- light green, tab titles and generic highlighting
+	[">"]="|r" }
 local T={}
 T.about = [[
 Ouro Loot is the fault of Farmbuyer of Ouroboros on US-Kilrogg.  Bug reports,
@@ -470,10 +477,42 @@
 "gray"/"grey" are all the same, "4", "epic", "purple" are the same, and so on.
 ]]
 
+T.tips_prescan = [[
+When loot is manipulated, the history of previous loot entries must be scanned
+to determine whether you already have any information for that loot.  In this
+case, "loot manipulation" includes things like receiving loot broadcasts from
+other players, marking older loot as being disenchanted, and so on.
+
+You can speed up these actions by turning on the +Prescan for faster handling>
+toggle on the <Options> tab.  This is a tradeoff:  loot manipulation will
+go faster, but data from the prescan will use up more memory.  (If you end up
+doing things to every single piece of loot, you would use up all that memory
+eventually.  But if you don't, then that memory is essentially wasted.)
+
+This prescanning is only done for the specific realm on which you're playing.
+Much depends on how far back you preserve history.  The more history you keep
+for a given realm, then...
+
+[option on] ...the more memory this option uses...
+
+[option off] ...the longer loot work takes...
+
+...while manipulating loot for that realm.  See the tradeoff?
+
+The prescan is only done once, during login.  It will print out how much
+additional memory is used, so you can better decide whether this option is
+worth turning on.  This also means that you need to relog or /reload to have
+the option take effect once you enable it.
+]]
+
 T.todo = [[
 If you have ideas or complaints or bug reports, first check the Bugs subcategories
 to see if they're already being worked on.  Bug reports are especially helpful
-if you can include a screenshot (in whatever image format you find convenient).
+if you can include a screenshot (in whatever image format you find convenient),
+and a copy of your SavedVariables file.  This is found in your World of Warcraft
+installation folder, named "WTF/Account/you/SavedVariables/Ouro_Loot.lua"
+(where "you" is your account name).  You may need to compress this file
+before the ticket system will accept it.
 
 Click the "About" line on the left for contact information.
 ]]
@@ -482,6 +521,10 @@
 <Things Which Might Surprise You> (and things I'm not sure I like in the
 current design):
 
+Manipulating existing information while logged into a realm other than the
+realm represented by that same information can yield strange results, including
+outright breakage.
+
 If you relog (or get disconnected) while in a raid group, behavior when you log
 back in can be surprising.  If you have already recorded loot (and therefore
 the loot list is restored), then OL assumes it's from the current raid and should
@@ -494,12 +537,6 @@
 the full loot list.  Restoring will get you a blank first tab and whatever you
 previously had in the various generated text tabs.
 
-Using the right-click menu to change an item's treatment (shard, offspec, etc)
-does not broadcast that change to anyone else who is also tracking.  Changing
-the item and then selecting "rebroadcast this item" <does> include that extra
-info.  Automatically doing that on the initial "mark as xxx" action would
-be... tricky.
-
 The generated forum text tries to only list the name of the instance if it has
 not already been listed, or if it is different than the instance of the previous
 boss.  If you relog, the "last printed instance name" will be forgotten, and