The upgrade is claimed to be seamless when running Lit 2.x with no deprecation warnings; defaulting to deprecated API documentation is a bit counterproductive.
If v3 is "not released" then having it accessible with the other 2 releases is contradictory - this "prerelease" is still a form of release; no claim was made that the entirety of the v2 documentation was deprecated.
> no claim was made that the entirety of the v2 documentation was deprecated
> defaulting to deprecated API documentation
I am not sure what point is being made here. This seems to be splitting hairs.
Regardless, it makes sense to default to the docs for the version which is considered to be officially released. That version is probably most likely to be used in a production application, which is usually what the docs are intended to support.
