* 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
[Internal review URL](https://review.docs.microsoft.com/en-us/aspnet/core/signalr/security?view=aspnetcore-2.1&branch=pr-en-us-9088)
- Kill long sentences. Long sentences are difficult for native speakers and impossible for MT (machine translation)
- Format code to prevent horizontal scroll bar on tablets 85 characters wide. You can simulate tablets by viewing in a browser of the maximum width that doesn't have left or right panes (TOC's).
- Prune dead wood. Avoid unnecessary words that don't add meaning to the text.
- Avoid "you" except when it make the statement more clear.
- For example, the following CORS policy allows a SignalR browser client hosted on `http://example.com` to access **your** SignalR app:
-For example, the following CORS policy allows a SignalR browser client hosted on `http://example.com` to access the SignalR app hosted on `http://signalr.example.com`:
- Avoid Wikipedia links
- Code snippets
Explicit sign-off required on my security rewording below:
- [ ] Allow cross-origin requests only from domains you trust or control.
The following are slightly too long but I couldn't find an elegant way to shorten them (not that my other trimming was elegant):
- Applications should be configured to validate these headers to ensure that only WebSockets coming from the expected origins are allowed.
Addresses #8579
I might be getting the hang of **_find and replace_** now. 😝
This doesn't touch a couple that ref 2.2.0. I'll tidy those up on https://github.com/aspnet/Docs/issues/8518 after 2.2 RTM.
Fixes#8505
Added the section to signalr/hubs.md for Hub<T>. Added a refactored version of `ChatHub` to use an interface instead of `SendAsync`.
Any feedback is greatly appreciated! My first PR to docs!
* Update dotnet-client.md
remove double send
Remove `you` when it doesn't add clarity. You aren't sending/receiving, the client is. It's more clear without you.
* simplify intro
* Fix SignalR .NET client sample app
* Adjust line numbers in associated doc
* Fix HintPaths
* Convert packages.config to PackageReferences
* Add launchSettings.json to ensure same port WPF app expects is used
Brady Gaster
Ahmed Yahia
Andrew Stanton-Nurse
BrennanConroy
Tom Dykstra
Mikael Mengistu
Sean 'Doc' Rinehart
Rick Anderson
Nytiennzo Madooray
Scott Addie
Antoine Griffard
Luke Latham
Cecil Phillip
José Maia
Kevin Griffin