Chapter in question: https://github.com/getify/You-Dont-Know-JS/blob/master/es6%20%26%20beyond/ch2.md#template-literals

The suggestion seems to be that the template literals would be all about strings; there's only examples that result in strings, and phrases like "final string value" and "generating the string from the literal" are used in what should be a general context, but the tag function

Of the three examples here only hash correctly reports if an executable is in the PATH. type -p and command -v both report success on aliases, builtins, etc.

type -P (capital P) does correctly report if an executable is in the PATH.

Perhaps this section could

It says that python gets left to point to the system python (2.7 on OSX), but then goes on to say that python points to homebrew Python3.

https://github.com/realpython/python-guide/blame/master/docs/starting/install/osx.rst#L84-L89

Not sure which bit needs to be changed.

explanation behind that says it's just coercion of one type plus another.
What is happening there is actually a code block and a unary + which coerces the array into 0.
({} + []) would get the same as ([] + {}) understandably.

I think you make a very solid point in that section when you say that:

I do think you should be careful about the flow control part of return creating more implicitness in your function definitions. Try to figure out the most explicit way to express the logic; that will often be the best way.

But in your example I feel you do just the opposite. You add an extra variable that I need to keep t

The input system usually includes a mouse and a key-board, while the output system usually consists of a monitor that can display a large mount amount of pixels.

Right now it's just a collection of links (the basic format of each entry is 'name - author'). It might be helpful to make room for 1-2 sentence explanations of the link, particularly as the list grows.

(PS this project is linked prominently from the website now)

At the section Attribute-like macros the implementation of the proc_derive_attribute macro should not be blank, showcasing the minimum functional example since args are parsed differently and it's shown the implementation of a simple derive at the section above it.

Moreover, it needs to be mentioned that an attribute macro replaces the "thing" they annotate (lost a ton of time in this yeste

v09 chapter about HMMs refers to "gait" and "gate."

I think it should just be "gait?"

Identifying people based on their gait is a pretty cool idea, but first we need a model to
recognize the gate. Consider a HMM where the sequence of hidden states for a gate are

s/gate/gait/g