[cvas22]

Following the discussion in #3431, this changes "re-authentication" to "reauthentication" (and "re-authenticate" to "reauthenticate") in the V7 chapter and the glossary, which are the only places it appears in the source. That matches NIST SP 800-63B, which 7.1.1 points to, and the style guides @nnsee looked at. There are no other forms of the word in the source, so the spelling is now consistent.

Wording only, the requirements don't change. I left the generated 5.0.0 files in docs_en alone.

Closes #3431

[elarlang]

PR marked as draft because:

• there is no agreement in the issue
• the issue is not marked as "Awaiting PR"
• there are no modification tags.

See: https://github.com/OWASP/ASVS/blob/master/CONTRIBUTING.md

[cvas22]

@elarlang re-authentication vs reauthentication: Both are generally accepted. However, tech firms (US) typically use the latter, and so does the NIST standard as previously linked. If a maintainer feels otherwise, happy to close this PR. At this point, it's purely a preference/style guide IMO.

Here's another example of "Resynchronization" on the RFC Standard