-
Notifications
You must be signed in to change notification settings - Fork 144
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
Update package descriptions and some links in docs #587
Conversation
Had a lengthy conversation with native English speaking tech writers about "needed vs necessary" recently. It's much better to use "necessary" in such situations as it is as a legit adjective and "needed" is perceived as a verb forced to act as an adjective in their eyes. That's not a set-in-stone rule, but "necessary" is just better here.
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.
Looks cool, thank you 👍
(I'd probably drop “and wrappers” in all of the “...and has a unified API and wrappers across 12 platforms” since the users are probably not that interested in our internal lingo of wrapper/binding/library/extension, but “unified API across 12 platforms” reads as something substantial. Just my 2¢)
P.S. One day I'll get GitHub Actions CI done and README edits won't trigger full repository rebuild...
Thank you for the review! Hmm, I could be biased, too as I keep seeing the word "wrapper" with the very same meaning that we attach to it, across numerous unrelated projects. |
rm "wrappers"
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.
@karenswry do you plan to add anything to this PR, or we can merge it?
Done here. Please merge. |
Ruby gems and iOS pods-related changes + a touch of T1345 (slight changes in bug report and pull request templates).
Checklist