Fix some confusing documentation noticed by Jason McDonald at AFIT

assign/anneal.cc

@@ -478,7 +478,8 @@ void anneal(bool scoring_selftest, double scale_neighborhood,
 #endif
 
   /*
-   * Calculate the number of iterations to stay at this temperature step
+   * When melting, this is the number of different solutions we will try during
+   * this temperature step
    */
   melt_trans = neighborsize;
   

assign/compile-options.txt

@@ -133,8 +133,7 @@ PER_VNODE_TT		Normally, assign keeps a 'type table' indicating which
 			helpful information up-from about which nodes cannot
 			be mapped, and could be used to prune down the size of
 			the search space, since we can ignore nodes that are not
-			in any node's TT. Unfortunately, breaks vclasses, so 
-			it's off for now
+			in any node's TT.
 SMART_UNMAP		When assign decides that it needs to unmap some existing
 			mapping, because there are no potential matches for a
 			vnode, causes it to intelligently unmap a pnode that