anchor.diff:  %% <p> Usage: Select the refactoring command, and Wrangler will check the current type of the state machine, 
   %% and prompt you to input the record and field names if Wrangler is able to proceed the refactoring.
   %% </p>
  -%% @spec eqc_statem_to_record(FileName::filename(),SearchPaths::[dir()], TabWidth::integer()) ->
  -%%               {error, string()} |
  -%%		 {'ok', non_tuple, [{atom(), atom(), integer()}]} |
  -%%		 {'ok', {tuple, integer()}, [{atom(), atom(), integer()}]}
  +
   -spec(eqc_statem_to_record/3::(filename(),[dir()], integer()) ->
   	         {error, string()} |
   		 {'ok', non_tuple, [{atom(), atom(), integer()}]} |
  
positive.code: %% function name, then select <em> Rename Function Name </em> from the <em> Refactor </em> menu, 
  %% after that, Wrangler will prompt to enter  the new function name in the mini-buffer.
  %% </p>
  %% @spec rename_fun(FileName::filename(), Line::integer(), Col::integer(), NewName::string(), SearchPaths::[dir()], TabWidth:: integer())
  %% -> {error, string()} | {ok, [filename()]}
  -spec(rename_fun/6::(string(), integer(), integer(), string(), [dir()], integer()) ->
  	     {error, string()} |{warning, string()}| {ok, [filename()]}).
  rename_fun(FileName, Line, Col, NewName, SearchPaths, TabWidth) ->
  
negative.code: %% <p> Usage: to apply this refactoring, highlight the arguments to be grouped into a tuple from 
  %% the function definition, then select <em> Tuple Function Arguments </em> from <em> Refactor</em>.
  %% </p>
  
  -spec(tuple_funpar/5::(filename(), pos(), pos, [dir()], integer()) ->
  	     {error, string()} | {ok, [filename()]}).
  tuple_funpar(FileName, StartLoc, EndLoc,SearchPaths, TabWidth) ->
  