Skip to content
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

Corrections from Lloyd #39

Open
choptastic opened this issue Aug 29, 2017 · 0 comments
Open

Corrections from Lloyd #39

choptastic opened this issue Aug 29, 2017 · 0 comments

Comments

@choptastic
Copy link
Member

Hi Jesse,

I'm reading through on my iPad so can't immediately fix stuff as I come across it. So I'm sending this list to both of us with hope that someday the issues will be fixed.

p 83 -- this with with more han
p 85 -- wf:defer (should this be ital?)
p 86 -- than one submitted fields with the (should be field)
p 88 -- %% ‘Person‘ wi (fussy, but to be typographically correct, should be open and close single quotes)
p 90 -- Way back in the day when I was hosting my Super Awsome HomepageTM on the now defunct GeoCities was the cutting edge ability to change an image source on the fly (usually when hovering over th (GeoCities, the ability ... fly was cutting edge (usually...))
P 93 -- But we model the pages as if they records. Since we’re doing Nitrogen, and it’s good to think in Nitrogen elements. (Fix garbled syntax)
p 100 -- authmatically
p 101 -- which as mentioned on A, is great for IO purposes (A?)
p 104 -- Note NOTE
p 104 -- 4See page404 (Need space after 'page'
p 105 -- It will always ("It" looks like it's set in bf)

p 118 -- And we can do that how. (Should have ? rather than .)
p 118 -- It’s a wonky, (Delete a)
p 123 -- What happens if a user is tries to UPDATE (Delete is)
p 123 -- record. 15So we (Fix spaces)
p 125 -- "sticking an element in front of a list"? (This looks like one long noun. Should be "sticking_an_element_in_front...)
p 125 -- C/Java-like Pseudocode (lower-case p)
p 126 -- Note NOTE
p 129 -- RUSTY: Good to go (Delete)

Chapter 6 seems very long. I suggest that break it to a new chapter at 6.7; e.g. Everything from 6.7 through to the end of the current chapter 6 becomes chapter 7.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant