Historical errata for Swift Style

“To give you a sense this scope,” -> “To give you a sense of this scope,” (missing “of”)

“I call the mixed Alman-1TBS style” -> “I call the mixed Allman-1TBS style”

The name “Allman” is missing an L.

(on line 1)
you can pass often pass -> you can often pass

The mobi version does not correctly indent in the Kindle app on iPad. This is crucial for the first chapter about proper indentation. I first thought: what an odd way to indent by not indenting at all. When I opened the epub in iBooks I saw the correct indentations.
Cheers,
Markus

Chapter 3, " .​lazy​.prefix(while: { value <= 128 })"

Should read: .​lazy​.prefix(while: { $0 <= 128 })

Chapter 3 “Swift code rarely uses `while` and `repeat-while` loops. The most common use case is `while true` that drives a infinite or breakable loop. ”

Drives an infinite not drives a infinite

I use “the result is simpler and cleaner” twice within the chapter.

SUGGESTED FIX: Change second one from “Prefer `forEach` to `for-in` when you can apply a function reference to each member of a sequence. The result is simpler and cleaner:” to “Prefer `forEach` to `for-in` when you can apply a function reference to each member of a sequence:”

Mandatory self has been adopted by a non-negligible large and worthy organizations.

FIX: Mandatory self has been adopted by a non-negligible number of large and worthy organizations.

“And here is a more general version of with that supports value types. This alternate approach allowing creating modified versions of constants”

s/allowing/allows/

A few Swift developers move in to its own,
should read:
A few Swift developers move in to its own line,

In last paragraph, I believe that “more flexibility” should be changed to “more flexibly”.

Adding a well-stated assertion failure ensures your assumptions about exhaustive cases was properly founded.
->were properly founded.

“prefer mentioning every case than catching final cases with default”. This seems to take the construction “prefer X than Y”, but I think typically you’d say “prefer X to Y.” So “prefer mentioning every case TO catching final cases with default”

Under “Chaining Calls”, `myInstance.surname.characters.count` is referred to as a fluent interface. The implication seems to be that any call chain is a fluent interface. But the Wikipedia page in the footnote says that a fluent interface entails more than just method chaining. Martin Fowler’s bliki page on the term says that typically fluent interfaces are used for configuring objects, and that the key is that they’re providing a domain-specific language. It seems to be primarily for setters, not for getters. So it doesn’t seem to me that just drilling into properties of objects qualifies as a fluent interface. At the very least, it’s debatable whether that term applies, so it may be best to qualify it.