Concurrency > Sendable Types — Clarify intro about non-sendable data about swift-book HOT 4 OPEN

I'm looking at the paragraph, and I wonder if we need this sentence at all. I think I wrote it to introduce the problem before showing the solution, but maybe it better for me to rewrite and remove this.

A paragraph later, we say essentially the same thing:

In contrast, some types aren’t safe to pass across concurrency domains.

from swift-book.

I see that 'overlapping access' is defined later in the book under the 'memory safety' section.

However, I still find the sentence confusing.

from swift-book.

This sentence should avoid the phrase "overlapping access" — the meaning here isn't exactly the same as how Memory Safety later uses it. Here we mean access from different parts of the program that are running concurrently.

from swift-book.

So, would the following version of the sentence be more suitable?

Some kinds of data can’t be shared between concurrency domains, because that data contains mutable state, and is not protected against concurrent access.

from swift-book.