VeraCrypt
aboutsummaryrefslogtreecommitdiff
path: root/doc/html/Hidden Volume.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/Hidden Volume.html')
-rw-r--r--doc/html/Hidden Volume.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/html/Hidden Volume.html b/doc/html/Hidden Volume.html
index 56f38e2b..bb415d36 100644
--- a/doc/html/Hidden Volume.html
+++ b/doc/html/Hidden Volume.html
@@ -46,7 +46,7 @@ It may happen that you are forced by somebody to reveal the password to an encry
<div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
<br style="text-align:left">
The principle is that a VeraCrypt volume is created within another VeraCrypt volume (within the free space on the volume). Even when the outer volume is mounted, it should be impossible to prove whether there is a hidden volume within it or not*, because free
- space on <em style="text-align:left">any </em>VeraCrypt volume is always filled with random data when the volume is created** and no part of the (dismounted) hidden volume can be distinguished from random data. Note that VeraCrypt does not modify the file
+ space on <em style="text-align:left">any </em>VeraCrypt volume is always filled with random data when the volume is created** and no part of the (unmounted) hidden volume can be distinguished from random data. Note that VeraCrypt does not modify the file
system (information about free space, etc.) within the outer volume in any way.</div>
<div style="text-align:left; margin-top:19px; margin-bottom:19px; padding-top:0px; padding-bottom:0px">
<br style="text-align:left">