Julia Evans proposed replacing the checkout documentation's detached HEAD explanation with a new standalone guide. Her commit message lists problems with the current text. It says detached HEAD is useful without explaining why, takes many paragraphs to say what it is, does not say why users end up there accidentally, and does not mention that git switch makes accidental detaching harder. It also uses too many confusing diagrams. A standalone guide could be referenced from advice messages.
Junio Hamano's comments focus on how to describe HEAD. He said that "from which your current changes started" captures it: HEAD is where you started from and can return to, the next commit is built on it, and that commit then becomes the current one. He thinks it is useful for users to realise HEAD is where you started, regardless of where you are going.
Hamano said he appreciates one addition, apparently the last two lines of a passage. However, he said the text should avoid saying it is "useful for HEAD to be a commit ID". In his view the notable characteristic of a detached HEAD is that it refers directly to a commit, not that it is a commit ID.
D. Ben Knoble, who said he wants the manual to land, summarised the state of the thread. Evans needs to send a reroll with the SQUASH??? commit Hamano posted, or something like it, and the discussion on how to describe HEAD must be resolved. He quoted Hamano's suggested wording next to the v4 text, which describes HEAD as holding either a current branch or a commit ID when there is no current branch.