doc/tag: candidate explanation of tag workflow

Some suggestions re: tag workflow.  Open to major revision/bikeshedding.

There is a distinction between 'tag' (eg a git tag) which identifies a specific release (and is very closely related to 'version') and 'dist-tag' which identifies both a stream of releases and the most current version in that release, but I am having a hard time articulating it.

Is the name "tag" or "dist-tag" still open to bikeshedding or is it basically set in stone?
Not sure this paragraph is necessary – the previous paragraph already includes some examples of valid semver ranges that aren't valid dist-tags, and I feel like this heuristic might be confusing. I could be persuaded either way, though.