title: Making JavaDoc robust against refactoring
body: <p>I'm working on an application which is constantly refactored to improve it. Now, if we rename a certain class to better capture its intention, all the documentation mentioning the class does not get updated automatically, unless you use links ({@link ClassName}) to refer to the class. </p>
  
  <p>JavaDoc principles however state that one should "Use in-line links economically", since links stand out and draw the readers attention, which I find sensible. Also you can't link to parameters of a method.</p>
  
  <p>Is there another way in JavaDoc to make comments more robust to refactoring I'm not aware of?</p>