updated link to assets

Author: DAILLY

2.CreateGenericCMK-CEK.md

@@ -189,15 +189,15 @@ You can now check the keys in SQL Server Management Studio. The result should be
 
 - CMK / CEK available
 
-![CMK/CEK available](assets\ssms_keys_creation.png)
+![CMK/CEK available](assets/ssms_keys_creation.png)
 
 - CMK Details
 
-![Generic CMK](assets\ssms_cmk_details.png)
+![Generic CMK](assets/ssms_cmk_details.png)
 
 - CEK Details
 
-![Generic CMK](assets\ssms_cek_details.png)
+![Generic CMK](assets/ssms_cek_details.png)
 
 <br />
 <br />
@@ -208,7 +208,7 @@ Now CMK and CEK keys are created in the database, the security administrator (wi
 
 - Data before encryption :
 
-![Data PlainText](assets\ssms_before_encryption.png)
+![Data PlainText](assets/ssms_before_encryption.png)
 
 ```PowerShell
 # set the CEK key name
@@ -238,7 +238,7 @@ Set-SqlColumnEncryption -ColumnEncryptionSettings $ces -LogFileDirectory $logdir
 
 - Data after encryption :
 
-![Data PlainText](assets\ssms_after_encryption.png)
+![Data PlainText](assets/ssms_after_encryption.png)
 
 - Log file result :
 

Issue1.md

@@ -73,7 +73,7 @@ By updating the IL Code from the original DLL, the SqlServer PowerShell module d
 
 There is 2 solutions for this:
 - Update by yourself the IL code, and while saving the modified DLL Reflexil will prompt to "Register it for verification skipping" :<br />
-![](assets\reflexil_verification_skipping.png)
+![](assets/reflexil_verification_skipping.png)
 
 - Use the already patched [System.Management.SQLServer.Management.dll](bin/Microsoft.SqlServer.Management.AlwaysEncrypted.Management.dll), and register the assembly to bypass Strong Name checking (using the sn.exe utility of the .NET SDK). The sn.exe utility is provided with the .NET Framework. Check a path like this one, depending the version of the .NET Framework installed "C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools".<br />
 Below are the following commands to: