-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Proof-reading of "So Whats Next" #1186
Commits on Feb 14, 2023
-
Configuration menu - View commit details
-
Copy full SHA for bf2cdc1 - Browse repository at this point
Copy the full SHA bf2cdc1View commit details -
Some places in post "2023-02-14-so-whats-next.md" use spaced hyphens, some use spaced m-dashes. Replace usages of spaced hyphen (-) with more appropriate m-dash (—) for consistency and readability.
Configuration menu - View commit details
-
Copy full SHA for 3203e5f - Browse repository at this point
Copy the full SHA 3203e5fView commit details -
use straight double quotes consistently
The post "2023-02-14-so-whats-next.md" uses a combination of straight double quotes ("") and curly double quotes (“”). Replace the only usage of curly ones with straight double quotes.
Configuration menu - View commit details
-
Copy full SHA for c6e5bf3 - Browse repository at this point
Copy the full SHA c6e5bf3View commit details -
use straight single quotes consistently
The post "2023-02-14-so-whats-next.md" uses a combination of straight single quotes (') and curly single quotes (’). Replace all usages of curly ones with straight single quotes.
1Configuration menu - View commit details
-
Copy full SHA for fcaa5d5 - Browse repository at this point
Copy the full SHA fcaa5d5View commit details
Commits on Feb 15, 2023
-
copyedit 2023-02-14-so-whats-next.md
Fix wording in 2023-02-14-so-whats-next.md: add missing words, replace words, rearrange sentences, etc.
Configuration menu - View commit details
-
Copy full SHA for b2c5eeb - Browse repository at this point
Copy the full SHA b2c5eebView commit details -
[CI-SKIP] Proof-reading of "So Whats Next"
I was pretty liberal in my edits, tried to understand author's intentional words and rephrase them better in some places.
1Configuration menu - View commit details
-
Copy full SHA for 8d928eb - Browse repository at this point
Copy the full SHA 8d928ebView commit details
Commits on Feb 18, 2023
-
so-whats-next: Proof-reading, corrections part 1
Changes up to 23:28, excluding the donations chapter
Configuration menu - View commit details
-
Copy full SHA for 32f64c6 - Browse repository at this point
Copy the full SHA 32f64c6View commit details
Commits on Feb 19, 2023
-
Merge branch 'grammar-fixes' of https://github.com/rybak/core-js into…
… rybak/grammar-fixes Since this is a natural text with multiple options, this merge commit actually changes some sentences to accomodate both suggestions. The dash changes were kept where possible. The single- and double-quote changes were not respected during merge, because I did not read Rybak's commit messages; they're indeed inconsistent.
Configuration menu - View commit details
-
Copy full SHA for e83d5ef - Browse repository at this point
Copy the full SHA e83d5efView commit details -
so-whats-next: Use m-dash, quotes consistently
Fix up after the previous merge. This includes the left over m-dash, single quotes, double-quotes.
Configuration menu - View commit details
-
Copy full SHA for 475bd06 - Browse repository at this point
Copy the full SHA 475bd06View commit details