"Thread safety" is more than just protection against data races, which (AFAIK--I am quite happy to acknowledge being wrong here) is the guarantee Rust makes.
Part of the issue with that slogan is that "thread safety" doesn't have any specific definition. Yes, we're specifically talking about data races, as well as the general Send/Sync bounds, but for a blurb on the home page, "thread safety" is the best thing we could come up with. Pitches need to be succinct and get the idea across, but due to the succinctness, can't capture 100% of the details.
No doubt, and I wasn't intending to ding the docs. Rust docs are a paradigm to be emulated in almost every case in my opinion.
None taken! This issue has come up on HN before, just trying to clarify and support what you were saying.