anchor.diff:  %% If the user answers 'yes' to one instance,  that instance will be replaced by function application,
   %% otherwise it will remain unchanged.
   %% </p>
  -%% <p> In the case that a candidate expression/expression sequence  need to export some variables which 
  +%% <p> In the case that a candidate expression/expression sequence  needs to export some variables which 
   %% are used by the following code, that expression/expression sequence will be replaced by a match 
   %% expression, whose left-hand side it the exported variable(s), and right-hand side is the function
   %% application.
  
positive.code:     try_refactoring(refac_rename_var, rename_var_eclipse, [FileName, Line, Col, NewName, SearchPaths]).
  
  %%=========================================================================================
  %% @doc Rename a function name with a user-supplied new name.
  %% <p> To apply this refactoring, point the cursor to any occurrence of this 
  %% function name, then select <em> Rename Function Name </em> from the <em> Refactor </em> menu, 
  %% after that the refactorer will prompt to enter  the new function name in the mini-buffer.
  
negative.code:     refac_expr_search:expr_search(FileName, Start, End).
  
  %% =====================================================================================================
  %%@doc Introduce a new function to represent an expression or expression sequence selected by the user.
  %% <p> This refactoring allows the user to introduce a new function to represent a selected expression or expression 
  %% sequence, and replace the selected expression/expression sequence with a call to the new function.  Those free variables
  %% within the expression/expression sequence become the formal parameters of the function.
  