Errata
The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
Version | Location | Description | Submitted by | Date submitted |
---|---|---|---|---|
Printed | Page 5 7th paragraph |
Under the "Access" sub-heading, first sentence starts as "Do you need to be have...". This probably should be "Do you need to have..." |
Anonymous | Mar 22, 2018 |
Printed | Page 8 5th paragraph, last sentence |
"render it mute" should be "render it moot" meaning that it is rendered irrelevant versus what is printed in the book which means that it is rendered speechless. |
Anonymous | Mar 22, 2018 |
Printed | Page 10 5th paragraph, 2nd sentence |
"...in which is is modified..." should be "...in which it is modiifed..." |
Camille Kloppenburg | Mar 22, 2018 |
Printed | Page 78 Last paragraph, first sentence (under Availability sub-header) |
There is an errant hyphen before "at the network." |
Anonymous | Jul 29, 2019 |
Printed | Page 335 3rd paragraph |
In "to continue to illicit engagement from the organization", "illicit" should be "elicit". |
James Juran | Jan 01, 2018 |
Mobi | Page 528 Location in Kindle edition, last sentence in sidebar box |
Jez Humble's name is Jez Humble, not Jezz. |
James Abley | Sep 18, 2017 |
Mobi | Page 1229 top of location (mobi) |
Small grammar error that makes the intended point difficult to understand. "But Agile methods have a difficult time dealing with nonfunctional and cross-functional requirements, but": one of the buts is probably incorrect. |
Douglas MacIver | Oct 17, 2017 |