Skip to content

Commit

Permalink
Fix grammar in at risk marker for multibit status.
Browse files Browse the repository at this point in the history
Co-authored-by: Ted Thibodeau Jr <[email protected]>
  • Loading branch information
msporny and TallTed committed Jan 13, 2024
1 parent 6eca6fb commit f812b4b
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 9 deletions.
4 changes: 2 additions & 2 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,9 +9,9 @@ in the relevant W3C Working Group or make a non-member patent licensing
commitment.

If you are not the sole contributor to a contribution (pull request), please
identify all contributors in the pull request comment.
identify all contributors in the pull request comment.

To add a contributor (other than yourself, that's automatic), mark them one per
To add a contributor (other than yourself; that's automatic), mark them one per
line as follows:

```
Expand Down
14 changes: 7 additions & 7 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -462,13 +462,13 @@ <h3>BitstringStatusListCredential</h3>

<p class="issue atrisk"
title="Bitstring entry sizes greater than 1 are at risk.">
The Working Group is currently seeking implementer feedback with respect to the
usefulness of bitstring entries that have sizes greater than one. The
approach adds complexity to the solution and its not clear if there is
enough of an implementation community to support the feature. The WG is
considering three options 1) keep the feature, 2) allow the feature to be
optionally supported, and 3) remove the feature. At present, the specification
implements the second option.
The Working Group is currently seeking implementer feedback regarding the
utility of bitstring entries that have sizes greater than one. Supporting
such entries adds complexity to the solution, and it's not clear whether there
is enough of an implementation community to support the feature. The WG is
considering three options: (1) require conforming implementations to support
the feature; (2) allow implementations to optionally support the feature; or
(3) remove the feature. At present, the specification implements option (2).
</p>

<table class="simple">
Expand Down

0 comments on commit f812b4b

Please sign in to comment.