fix typos in spec #387
Merged
fix typos in spec #387
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Great cleanup, thank you! I'll add a couple of tiny in-line comments. |
dglazer
reviewed
Sep 12, 2022
| @@ -15,6 +15,6 @@ properties: | |||
| Other values MAY be used, as long as implementors are aware of the issues discussed in https://tools.ietf.org/html/rfc6920#section-9.4[RFC6920]. | |||
|
|
|||
| GA4GH may provide more explicit guidance for use of non-IANA-registered algorithms in the future. | |||
| Until then, if implementors do choose such an algorithm (e.g. because it's implemented by their storage provider), they SHOULD use an existing | |||
There was a problem hiding this comment.
either spelling is acceptable; I agree "er" is more common
dglazer
reviewed
Sep 12, 2022
| @@ -8,7 +8,7 @@ See the documentation on the [n2t.net](https://n2t.net/e/compact_ids.html) and [ | |||
|
|
|||
| ## Calling Meta-Resolver APIs for Compact Identifier-Based DRS URIs | |||
|
|
|||
| Clients resolving Compact Identifier-based URIs need to convert a prefix (e.g. “drs.42”) into an URL pattern. They can do so by calling either the identifiers.org or the n2t.net API, since the two meta-resolvers keep their mapping databases in sync. | |||
There was a problem hiding this comment.
I personally prefer "an", since I read it to myself as "an earl", not as "a you are ell". But the Web agrees with you (32M vs. 1M).
briandoconnor
approved these changes
Sep 22, 2022
There was a problem hiding this comment.
This is great!! Thanks @Shakespeared so much for doing this!!
Thanks for reviewing and merging, glad it was helpful! :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No functional changes, just typos
#386