Fix https://github.com/aspnet/Docs/issues/10636
### Question
@Rick-Anderson
Under 7f52e7646a/aspnetcore/mvc/views/view-components.md (specifying-a-view-name)
I don't know why there is the sentance`Update Views/ToDoList/Index.cshtml:` Maybe we must say instead `Update Views/ToDo/Index.cshtml:`
Furthermore, there is a comment ` <!-- Views/ToDoList/Index.cshtml is never imported, so change to test tutorial -->` . But the Views/TodoList doesn't exist ? Should we delete this comment?
Sorry, I don't understand well…
* Update About.cshtml
The WebsiteContext instance was initialized inside a C# code block to avoid a possible problem when one of its attributes is a string.
* Update authoring.md
Update highlights and ranges after updating the relevant source code:
authoring/sample/AuthoringTagHelpers/src/AuthoringTagHelpers/Views/Home/About.cshtml
Fixes#10264
[Review URL](https://review.docs.microsoft.com/en-us/aspnet/core/mvc/models/validation?view=aspnetcore-2.2&branch=pr-en-us-10390)
* Not too keen on "top-level node." It isn't documented anywhere, and Google Fu wasn't much help either. I've *guessed* from the API what it means (and I could be *wrong*).
* Side note: `Required` is *required* as a model property attribute to get client-side required validation to work AFAICT. Adding `Required` or `BindRequired` to the top-level node (parameter) doesn't make it work client-side. Not sure if that's an issue or not ... just a side behavior that I noticed when testing.
* `jQuery.validate()` doesn't seem to be a thing any longer. JS complains that it can't find the function with the most recent jQuery validation scripts (from the current templates). Everything seems to work without it, so I nixed it.
* The sample was *almost* updated for 2.2. This should take it across the finish line. 🏁
* In the OP, the dev said that they were missing `AddDataAnnotations`, but we don't doc that level of detail. If they go `AddMvcCore`, they're kind'a on their own to make sure that they have all of the bits in place.
* Add example of asp-area with a Razor Pages area
* Minor edits
* Fix code snippet include
* Add example of AllowAreas property
* Update aspnetcore/mvc/views/tag-helpers/built-in/anchor-tag-helper.md
Co-Authored-By: scottaddie <10702007+scottaddie@users.noreply.github.com>
Fixes#9336
<!--
When creating a new PR, please do the following:
* Reference the issue number if there is one, e.g.:
Fixes #Issue_Number
The "Fixes #nnn" syntax in the PR description allows GitHub to automatically close the issue when this PR is merged.
NOTE: This is a comment; please type your descriptions above or below it.
-->
Fixes#6971
<!--
When creating a new PR, please do the following:
* Reference the issue number if there is one, e.g.:
Fixes #Issue_Number
The "Fixes #nnn" syntax in the PR description allows GitHub to automatically close the issue when this PR is merged.
NOTE: This is a comment; please type your descriptions above or below it.
-->
* overview
* whats new to end
* fix migration node
* split fundamentals, move to end
* glob & loc, get started
* security node name
* security section
* azure, client-side, host
* several more sections
* redistribute tutorials
* proofread fixes
* move how to download section
* index files delete and redirect
* fix errors
* reorder some nodes
* scott feedback, flatten main tutorials node
* fix missed feedback items + other issues
* unflatten tutorials node
* move 'how to download'
* more tutorials node tweaks
* standardize view sample links
* db --> DB
* fix build error
* remove link from a parent node
* streamline node names
* xref links
* typos
* typo
* typos and revert some xref links
* scott feedback
* scott feedback
* feedback
* change node name
* safe storage-->protect
Fixes#9219
@JunTaoLuo Dan calls out the implicit versioning "for 2.1 SDK or later;" however, we don't usually version the doc content by SDK release. We might need to say something for this update in the passage that I'm adding to the All topic (*aspnetcore/fundamentals/metapackage.md*) about which SDK version this applies to. I don't know if that's something that you would like to do or what version to call out.
I also remove the version from the samples. We also assume that devs are using the latest SDK with our samples.