-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
fix(content): unify usage of i.e. and e.g. #7653
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
fix(content): unify usage of i.e. and e.g. #7653
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
de313ef to
7ab0d94
Compare
7ab0d94 to
86e7f63
Compare
|
@avivkeller I have fixed all the other occurrences :) |
|
Lighthouse Results
|
|
@Uaitt can you rebase? We updated some checks recently, and they need to be applied here (but they won't fail). |
86e7f63 to
5863a1c
Compare
|
@avivkeller done |
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## main #7653 +/- ##
==========================================
+ Coverage 74.61% 74.62% +0.01%
==========================================
Files 96 96
Lines 7689 7689
Branches 192 192
==========================================
+ Hits 5737 5738 +1
+ Misses 1950 1949 -1
Partials 2 2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Description
This PR just corrects a small typo on the Node.js with WebAssembly article.
Basically,
iebecomesi.e.Why am I proposing this?
I am in the process or reading all the Node.js getting started articles, and I have seen that in all other places in the docs the form
i.e.is used (as seen here: https://github.com/search?q=repo%3Anodejs%2Fnodejs.org%20%22i.e.%22&type=code).While the form
iecan be considered correct, a widely accepted rule of thumb is to be consistent, so eitheri.e.orieeverywhere. (https://english.stackexchange.com/questions/407270/is-ie-acceptable-or-must-it-always-be-i-e)