New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace "could" and "might", Clauses 16-32. #4386
Conversation
@opensdh: Could you perhaps take a look at the filesystem changes? @geoffromer: Could you perhaps take a look at the atomics and threads changes? Thank you! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The filesystem
changes generally look fine, but I made a few minor comments (one of which is just caught up in the same file).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This generally looks good, but I should note that I haven't been active in SG1 since February (or in editorial work for several years).
Co-authored-by: Geoff Romer <gromer@google.com>
Co-authored-by: Geoff Romer <gromer@google.com>
… "risk" vs "possiblity" nuance of "might"
@CaseyCarter: could you perhaps take a look at the ranges and concepts, particularly with a view to whether "might->can" confuses risk with possibility? |
These changes editorially remove the words "could" and "might".
Please review this change carefully with the following goals:
Flag anything that seems even remotely non-editorial, e.g. even if the explanation provided by a Note becomes less useful or (more) misleading.
Also flag anything that could conceivably be worded better by a wider review.
I would like all remaining instances of "could" and "might" to be reviewed by CWG/LWG, so please don't hold back on rejecting anything at this point.