copy: clarify names of source levels

[zachariahcox]

related to: #1097 (comment)

Level 2

my initial thoughts are that we're trying to get across the following concepts:

teams can have more than one branch
teams may need to indicate that consumers can / should / must ignore commits on users/* and only ship commits on /releases/* because branches have different security postures
only some branches have protected history, IE, we allow force push to user branches.
the logical VSA for this rule would need to verify that "the previous revision id is reachable from this new revision id" (IE: there was no potential for data loss due to force push or repo hijack)

#1097 (comment)

Level 3

• content: source track draft: simplify and clarify level goals #1097 (comment)

[zachariahcox]

possible duplicate of: #1070, though this one is more broad.

[TomHennen]

I think the only level name that could maybe use some improvement is level 3. I bet once we have #1143 nailed down we can use that language in the title somehow.