v0.1 Spelling Errors And Proofreading #1

Cryptopone opened this Issue Nov 17, 2012 · 3 comments


None yet
4 participants

Reading through v0.1 of your book and noticed a couple of spelling errors and a difficult to follow sentence.

Spelling errors in the flow section (pg 9):

Discovered in the 1950’s [fact check] by [guy who did] when he was observing artists, especially
painters, who woudl would get so lost int heir in their work they could forget to eat, drink and lose track of time to the point of forgetting what day it is.

Difficulty following sentence in About Flow - Cost of Interruption (pg 17)

First, a programmer needs to make sure they are working off the latest version of the project. Then
they must whatever issue tracking system they’re using.
Having a clear goal is after all paramount
to achieving flow and getting anything done.

Spelling in Primer on Sleep Science (pg 20)

This is because the light coming off our screens is very white, aimed right at our eyes and usually
insanely bright because monitors are set to stupid brightness levels by default and most people forget
to changesdfsdf those.

Kopac commented Nov 17, 2012

A primer on sleep science, section Bright screens (pg 20)

One of the biggest factors in human sleep-wake cycle is natural lgiht light.

I also think the final sentence should have a comma before huh.
Because we aren’t sleepy, we might as well work huh work, huh?

@soulseekah soulseekah referenced this issue Nov 18, 2012


tiny typos #3


soulseekah commented Nov 18, 2012

Will try to submit patches for the other ones mentioned here once I get to them while actually reading.


Swizec commented Nov 19, 2012

Thanks for reporting the typos, I also seemed to have missed the [fact check] notes when reviewing before publishing. Oops :)

@Kopac The sleep stuff chapter is very rough and more a random collection of thoughts right now. It will likely get completely rewritten.

@soulseekah soulseekah referenced this issue Nov 23, 2012


tiny typos #6

@Swizec Swizec closed this Nov 27, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment