You need to document TAG usage in both 2.0 and 3.0 specs

[pm-david-simerly]

TAG is a really useful directive to organize specifications into different orders depending on precedence, importance, or whatever. The problem is that many of our engineers expect it to mean something else and misuse it, leaving it for the spec editors to clean up. It's a very simple directive to explain and useful to add to a spec. Please add it to your Swagger 2.0/OpenAPI 3.0 spec tutorials. Thx.