1 files changed, 25 insertions, 25 deletions
diff --git a/src/Readme.txt b/src/Readme.txt
index faf1683f..97678b5d 100644
--- a/src/Readme.txt
+++ b/src/Readme.txt
@@ -17,16 +17,16 @@ called 'TrueCrypt' or 'VeraCrypt'
 Contents
 ========
 
-I. Windows  
-   Requirements for Building VeraCrypt for Windows  
-   Instructions for Building VeraCrypt for Windows  
+I. Windows
+   Requirements for Building VeraCrypt for Windows
+   Instructions for Building VeraCrypt for Windows
 	Instructions for Signing and Packaging VeraCrypt for Windows
 
-II. Linux and Mac OS X  
-    Requirements for Building VeraCrypt for Linux and Mac OS X  
-    Instructions for Building VeraCrypt for Linux and Mac OS X  
+II. Linux and Mac OS X
+    Requirements for Building VeraCrypt for Linux and Mac OS X
+    Instructions for Building VeraCrypt for Linux and Mac OS X
 	Mac OS X specifics
-	
+
 III. FreeBSD and OpenSolaris
 
 IV. Third-Party Developers (Contributors)
@@ -65,7 +65,7 @@ issued by Thawte certification authority. At the end of each official .exe and
 .sys file, there are embedded digital signatures and all related certificates
 (i.e. all certificates in the relevant certification chain, such as the
 certification authority certificates, CA-MS cross-certificate, and the
-IDRIX certificate).  
+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
@@ -108,12 +108,12 @@ Instructions for Signing and Packaging VeraCrypt for Windows:
 
 First, create an environment variable 'WSDK81' pointing to the Windows SDK
 for Windows 8.1 installation directory.
-The folder "Signing" contains a batch file (sign.bat) that will sign all 
-VeraCrypt components using a code signing certificate present on the 
+The folder "Signing" contains a batch file (sign.bat) that will sign all
+VeraCrypt components using a code signing certificate present on the
 certificate store and also build the final installation setup.
 The batch file suppose that the code signing certificate is issued by Thawt.
-This is the case for IDRIX's certificate. If yours is issued by another CA, 
-then you should put the Root and Intermediate certificates in the "Signing" 
+This is the case for IDRIX's certificate. If yours is issued by another CA,
+then you should put the Root and Intermediate certificates in the "Signing"
 folder and then modify sign.bat accordingly.
 
 
@@ -135,8 +135,8 @@ Requirements for Building VeraCrypt for Linux and Mac OS X:
   and https://osxfuse.github.io/)
 - RSA Security Inc. PKCS #11 Cryptographic Token Interface (Cryptoki) 2.20
   header files (available at ftp://ftp.rsasecurity.com/pub/pkcs/pkcs-11/v2-20).
-  They are already included in the source tree under the directory PKCS11 but 
-  it is possible to override it using the environment variable 'PKCS11_INC'. 
+  They are already included in the source tree under the directory PKCS11 but
+  it is possible to override it using the environment variable 'PKCS11_INC'.
 
 
 Instructions for Building VeraCrypt for Linux and Mac OS X:
@@ -146,7 +146,7 @@ Instructions for Building VeraCrypt for Linux and Mac OS X:
 
 2) If you have no wxWidgets shared library installed, run the following
    command to configure the wxWidgets static library for VeraCrypt and to
-   build it: 
+   build it:
 
    $ make WXSTATIC=1 WX_ROOT=/usr/src/wxWidgets wxbuild
 
@@ -159,7 +159,7 @@ Instructions for Building VeraCrypt for Linux and Mac OS X:
    $ make
 
    or if you have no wxWidgets shared library installed:
-   
+
    $ make WXSTATIC=1
 
 4) If successful, the VeraCrypt executable should be located in the directory
@@ -172,21 +172,21 @@ built using the 'NOGUI' parameter:
 
    $ make NOGUI=1 WXSTATIC=1 WX_ROOT=/usr/src/wxWidgets wxbuild
    $ make NOGUI=1 WXSTATIC=1
-   
+
 On MacOSX, building a console-only executable is not supported.
 
 Mac OS X specifics:
 -----------------------------------------------------------
-   
+
 Under MacOSX, the SDK for OSX 10.7 is used by default. To use another version
 of the SDK (i.e. 10.6), you can export the environment variable VC_OSX_TARGET:
-	
+
 	$ export VC_OSX_TARGET=10.6
 
 
 Before building under MacOSX, pkg-config must be installed if not yet available.
 Get it from http://pkgconfig.freedesktop.org/releases/pkg-config-0.28.tar.gz and
-compile using the following commands : 
+compile using the following commands :
 
 	$ ./configure --with-internal-glib
 	$ make
@@ -195,9 +195,9 @@ compile using the following commands :
 After making sure pkg-config is available, download and install OSXFuse from
 https://osxfuse.github.io/ (MacFUSE compatibility layer must selected)
 
-The script build_veracrypt_macosx.sh available under "src/Build" performs the 
+The script build_veracrypt_macosx.sh available under "src/Build" performs the
 full build of VeraCrypt including the creation of the installer pkg. It expects
-to find the wxWidgets 3.0.2 sources at the same level as where you put 
+to find the wxWidgets 3.0.2 sources at the same level as where you put
 VeraCrypt sources (i.e. if "src" path is "/Users/joe/Projects/VeraCrypt/src"
 then wxWidgets should be at "/Users/joe/Projects/wxWidgets-wxWidgets-3.0.2")
 
@@ -224,8 +224,8 @@ IV. Third-Party Developers (Contributors)
 If you intend to implement a feature, please contact us first to make sure:
 
 1) That the feature has not been implemented (we may have already implemented
-   it, but haven't released the code yet).  
-2) That the feature is acceptable.  
+   it, but haven't released the code yet).
+2) That the feature is acceptable.
 3) Whether we need help of third-party developers with implementing the feature.
 
 Information on how to contact us can be found at:
@@ -253,7 +253,7 @@ source code.
 Trademark Information
 ---------------------
 
-Any trademarks contained in the source code, binaries, and/or in the 
+Any trademarks contained in the source code, binaries, and/or in the
 documentation, are the sole property of their respective owners.