Re: [webauthn] Inconsistencies in backup state flags (#1740)

Adding on to this, Bikeshed is reporting errors with the new text:

```
FATAL ERROR: Line 984 isn't indented enough (needs 1 indent) to be valid Markdown:
"   is allowed to be [=backed up=]. Backup eligibility is signaled in [=authenticator data=]'s [=flags=] along with the current [=backup state=]. "
FATAL ERROR: Line 985 isn't indented enough (needs 1 indent) to be valid Markdown:
"   Backup eligibility is a [=credential property=] and is permanent for a given [=public key credential source=]. "
FATAL ERROR: Line 986 isn't indented enough (needs 1 indent) to be valid Markdown:
"   A backup eligible [=public key credential source=] is referred to as a <dfn>multi-device credential</dfn> whereas one that is not "
FATAL ERROR: Line 987 isn't indented enough (needs 1 indent) to be valid Markdown:
"   backup eligible is referred to as a <dfn>single-device credential</dfn>. See also [[#sctn-credential-backup]]."
FATAL ERROR: Line 991 isn't indented enough (needs 1 indent) to be valid Markdown:
"   signaled in [=authenticator data=]'s [=flags=] and can change over time. See also [=backup eligibility=] and [[#sctn-credential-backup]]."
```

-- 
GitHub Notification of comment by emlun
Please view or discuss this issue at https://github.com/w3c/webauthn/issues/1740#issuecomment-1151632154 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 9 June 2022 21:15:50 UTC