I think this looks fine, but I'm assuming that Eric wanted something a bit more in depth judging by the original issue, so I'm going to refrain from approving for now.

Actually, the focus is on highlighting the differences between Python threads and other threads. This clearly illustrates the unique aspects of Python daemon threads, and I believe Eric won’t have any objections to this.

Well, IIUC, part the motivation was to document some of the concerns about daemon threads as well. This sort of tells you what to do with them, but not what's wrong with them.

So in the description, I described that join should be used to solve it.

That's not that useful though, because the whole point of a daemon thread is that you don't want it to join.

That's not that useful though, because the whole point of a daemon thread is that you don't want it to join

I'm not sure if the new change is appropriate, but it seems to avoid emphasizing the need to call .join(). But, right, daemon threads generally don't require waiting for their completion, but it still allows the user to call it on them.