VeraCrypt
aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorMeteor0id <34976212+Meteor0id@users.noreply.github.com>2019-11-02 01:06:02 +0100
committerMounir IDRASSI <mounir.idrassi@idrix.fr>2019-11-02 01:06:02 +0100
commitbb123bb3e8719d012884d144d326e5e8c8c15786 (patch)
tree483b58eb2c91f4b53bb841676b6a1523221318d1 /README.md
parent3ad7d8adb73b7fa70957c886972154ff17db740b (diff)
downloadVeraCrypt-bb123bb3e8719d012884d144d326e5e8c8c15786.tar.gz
VeraCrypt-bb123bb3e8719d012884d144d326e5e8c8c15786.zip
Start following IEEE 1541 agreed naming of bytes (#532)
* Start following IEEE 1541 agreed naming of bytes This standard exists to prevent any confusion about the actual number of bytes. It has been agreed on by experts and is being used more widespead these day. Let's start properly naming the number of bytes, which is absolutely important in disk encryption software. * Update LanguageStrings.cpp * Update UserInterface.cpp * kibibyte instead of kilobyte * kibibyte instead of kilobyte * MiB instead of MB * undo accidental deletions Odd indeed that two random lines were deleted in a previous commit. Probably happened when using a keyboard shortcut while editing the file. This fixes the issue. * Mb to Mib
Diffstat (limited to 'README.md')
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 877d103c..0a99475d 100644
--- a/README.md
+++ b/README.md
@@ -68,7 +68,7 @@ IDRIX certificate).
Keep this in mind if you compile VeraCrypt
and compare your binaries with the official binaries. If your binaries are
unsigned, the sizes of the official binaries will usually be approximately
-10 KB greater than sizes of your binaries (there may be further differences
+10 KiB greater than sizes of your binaries (there may be further differences
if you use a different version of the compiler, or if you install a different
or no service pack for Visual Studio, or different hotfixes for it, or if you
use different versions of the required SDKs).