Documentation Improvements

[CleanCut]

This is my quick attempt at improving the existing migration docs so that they follow conventions similar to the latest blog post (author attribution, doc links for interesting bare items). I also tried to make some wording more straightforward and fixed at least one typo.

/cc @cart

[cart]

I'm not a huge fan of adding attribution here:

1. Migration is a "negative" context. It is "work" we're making our users do. If we add attribution here, people might subconsciously (or consciously) blame @user for the work being done.
2. This doesn't showcase the features themselves, only how they break
3. We already have blog posts for attribution. I see no need to double up here.

[CleanCut]

Sure thing. It sounds like the migration guide is not an extension of the blog post, it's a separate document specifically for what to look out for during migration.

With that in mind, it sounds like I should remove the section about StopWatch? It's new, so there's nothing it should break.

Are you looking for more comprehensive documentation? Like tables of "this method signature" -> "that method signature" for Timer?

[cart]

With that in mind, it sounds like I should remove the section about StopWatch? It's new, so there's nothing it should break.

Yeah lets remove the StopWatch section as its an entirely new feature.

Are you looking for more comprehensive documentation? Like tables of "this method signature" -> "that method signature" for Timer?

I think what you currently have strikes a good balance between explicitness and terseness. It covers the common case explicitly and gives people a jumping off point for everything else. I think once you remove the attribution line we're good to go.