episodes/*md: implement semantic line breaks #22
Conversation
introduction.md: readability pass 2
benchmarking.md: readability pass 1
Makes maintenance easier.
computing-pi.md: readability pass 1
threads-and-processes.md: readability pass 1
Plus a few minor edits, which will show up when merging with other branches,
Plus fix punctuation, which may show again up when merging back into other branches
With other incidental fixes
I am resuming this merge after a very long break. The changes accepted are: * in most cases, one-line paragraphs are split in as many paragraphs as there are lines * in some cases, a sentence was split across line and has been merged into one * in a few case, I have edited for readability (half an error because there is a branch for it!) So be it
Sentences ending with full stop, exclamation marks and question marks are single lines. Done manually to stay on the side of caution: outcome prone to misses
🆗 Pre-flight checks passed 😃This pull request has been checked and contains no modified workflow files or spoofing. Results of any additional workflows will appear here when they are done. |
|
Hi Giordano, it's very nice that you want to do this, but we're also currently improving the material in some other places. This will for sure introduce some major merge conflicts. I'll have to wait merging this for the moment. Please contact me before doing too much work! |
@jhidding It's for free. It made my own fork cleaner and more consistent. So merge it when you see it fit. I have no schedule attached to this PR. Semantic line breaks make merges easier, by the way. It might be an idea that you implement those in your edits. Happy work! |
Objective: each document line contains a single sentence finishing with full stop, question or exclamation marks. This helps maintain the code using git diffs.