It's about that time ⏰.
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
lol @guardrex… does just need to get updated to be 2.1? @scottaddie
2.2
... and I'm inquiring with the team now on priority. Do you want to handle the updates?
btw --- I just made a tiny change to repoint the Browser Link link to our topic. That's when I saw that it was getting a bit stale here and there. https://github.com/aspnet/Docs/pull/9933
We don't update that topic. We update these

cc @scottaddie @tdykstra
I just thought that someone coming in for the first time to Core would get a head full of knowledge on _what not to do_ if this isn't updated to latest.
Maybe the answer is just to change the title to ASP.NET to ASP.NET Core 2.0 ... that would make it really clear to the reader what they're getting.
cc @scottaddie @tdykstra
I agree.
@guardrex ASP.NET to ASP.NET Core 2.x would be a more accurate title.
It's not written for any flavor is it ... e.g. All package.
@guardrex All of the docs within this node were intended to target the latest stable release. We haven't had time to update them all. Consequently, there's a mix of 2.0, 2.1, and 2.2 content in there.
I see what you mean ... it's a node name vs. topic name thing. However, the "Overview" topic link loads this topic with the name Migrate from ASP.NET to ASP.NET Core. It could still get "2.0" tacked on to it ... the topic is 2.0, and maybe a little misleading either left alone or with "2.x" on it. The node name can stay the same.
@isaac2004 If you're interested in helping out, this doc needs to be updated for 2.2.
@guardrex @scottaddie #9967 fixes this
Most helpful comment
Maybe the answer is just to change the title to ASP.NET to ASP.NET Core 2.0 ... that would make it really clear to the reader what they're getting.