Things that I found unclear:
* missing info where routes come from
* *that will be used for request processing* (the URL or the values?)
* URL vs link (better to use just one term?)
My version is longer. I tried to unify terminology and emphasize that Routing can do one op and its reverse.
The route templates/behavior template didn't have a proper column marker, and the minlength example in the route constraints table was inconsistent with the note.
* quick test
* quick test
* quick test
* Revert "quick test"
This reverts commit 91b07a3df5.
* Revert "quick test"
This reverts commit e44af19bb4.
* Revert "quick test"
This reverts commit 6872a1921d.
* Removed links to old api site
* Fixed link to H1
* quick fix
* Fixed link to H1
* reverted to match master
* removed random character.
* removed random unix character
* removed random unix character
* removed random UTF character
* removed random UTF character
* removed random UTF character
* removed random UTF character
* removed random UTF character
* removed random UTF character
* Quick fixes
* Update CONTRIBUTING.md
* removed random UTF character
* removed random UTF character
* Update routing.md
* Update validation.md
* Update overview.md
* Update linuxproduction.md
* Update web-publishing-vs.md
* Update sociallogins.md
* Update cors.md
* Update cross-site-scripting.md
* Update overview.md
* Update key-encryption-at-rest.md
* Update adding-model.md
* Update new-field.md
* Update validation.md
* Update first-web-api.md
* Update nano-server.md
* Update your-first-mac-aspnet.md
* Update linuxproduction.md
Guillermo López-Anglada
Charlie Chu
Don Kiely
Andy Pasic
Rick Anderson
Steve Smith
Nikita Pakhomov
Daniel Roth