GitLab

It's not the way it behaves currently but it's how I would like it to
behave, see #15043#note-44.

VeraCrypt uses "partition and drive" in some places and we'll do the
same in VeraCrypt Mounter. In the doc "partition or drive" is more
correct.

It's slightly different in nature than the other parameters but we're
asking for it in the exact same places.

I want the example to apply to the most common use case: encrypting a
whole USB stick but I understand from deda9224 that's it's confusing
to put it right after the sentence explaining that you can have multiple
partitions on a USB stick.

It would be possible to encrypt the whole USB stick even if the stick
were not split into partitions.

In `/doc/encryption_and_privacy/encrypted_volumes.mdwn` VeraCrypt is
referred to as a disk encryption *tool* rather than a disk encryption
*software*.

It's not the way it behaves currently but it's how I would like it to
behave, see #15043#note-44.

It was mostly repeating information that we already have in the
comparison table.

It was very clear to P4 that 'partition' didn't apply to her scenario in
Mission 3 because she was trying to unlock an entire disk and not only a
partition of it.

The previous ones mentioned the tool to be used instead of the goal to
be reached by the user. These ones should be easier to navigate.

During the user testing, everybody who looked for it had a hard time
finding it or even gave up.

- Replace TrueCrypt documentation on the command line.
- Adjust LUKS documentation to explain the alternative with VeraCrypt.