@turt2live is wrong here. JavaDocs that directly relate to a change in functionality belong in the PR that changes the functionality. Adding a ```@see``` tag would be appropriate to put into this PR.

The exception would only be (sometimes) when a PR is only on CB side (like javadocing that an event will now fire in an additional circumstance).