Rewrite "Tails doesn't magically separate your different contextual identities"
As a start:
- "contextual identities" sounds a bit like jargon to me.
- Maybe our example in the 1st paragraph could be improved.
- Maybe we could find a better title for this section.
- Maybe we should talk about activitites that you really don't want to be related if things go bad.
- "First, because Tor tends to reuse the same circuits, for example, within the same browsing session" could be improved.
- Nowadays Tor Browser has top-level isolation: visits to different websites are forced to use different circuits.
- We should either be more precise or drop this.
- "browsing requests" is jargon.
- "If you are facing a global adversary as described above, it might then also be in a position to do this correlation." is already covered elsewhere. See also #17869 (closed) for ongoing work.
- "security hole" → "security vulnerability". See https://tails.boum.org/contribute/how/documentation/style_guide/#vulnerability.
- "information about your session could be leaked": could we find an example to make this more clear?
- "shutdown and restart Tails": That's not enough to protect from the second thread is the user has a Persistent Storage.
- We should update the entire section to take into account the Persistent Storage: if people are using the Persistent Storage, they should have different Tails USB sticks for each identity or activity.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information