Updated documentation

Author: DAILLY

2.CreateGenericCMK-CEK.md

@@ -187,15 +187,15 @@ New-SqlColumnEncryptionKey -Name $cekName -InputObject $database -ColumnMasterKe
 
 You can now check the keys in SQL Server Management Studio. The result should be like the following screenshot.
 
-- CMK / CEK available
+- CMK / CEK available :
 
 ![CMK/CEK available](assets/ssms_keys_creation.png)
 
-- CMK Details
+- CMK Details (check the Key Store Provider and Key Path) :
 
 ![Generic CMK](assets/ssms_cmk_details.png)
 
-- CEK Details
+- CEK Details :
 
 ![Generic CMK](assets/ssms_cek_details.png)
 
@@ -240,7 +240,7 @@ Set-SqlColumnEncryption -ColumnEncryptionSettings $ces -LogFileDirectory $logdir
 
 ![Data PlainText](assets/ssms_after_encryption.png)
 
-- Log file result :
+- Log file result (for information) :
 
 ```
 9/10/2018 4:12:17 PM		INFO		MainThread		Logger initialized.
@@ -256,4 +256,5 @@ Set-SqlColumnEncryption -ColumnEncryptionSettings $ces -LogFileDirectory $logdir
 9/10/2018 4:13:27 PM		INFO		[dbo].[Patients]		Catch-up iteration #2 for table '[dbo].[Patients]' completed. Data migration is 99.9 % done.
 9/10/2018 4:13:28 PM		INFO		[dbo].[Patients]		Catch-up phase completed.
 9/10/2018 4:13:28 PM		INFO		MainThread		Finalizing data migration.
-9/10/2018 4:13:29 PM		INFO		MainThread		Deploying the specified encryption settings completed in 0d:0h:1m:12s.
+9/10/2018 4:13:29 PM		INFO		MainThread		Deploying the specified encryption settings completed in 0d:0h:1m:12s.
+```

Issue1.md

@@ -30,7 +30,7 @@ public static class AlwaysEncryptedManagement {
 }
 ```
 
-The main issue in this code is the default statement. Only an error is returned whenever you attempt to access a custom provider. Normally the code should behave as in the the "AZURE_KEY_VAULT" statement.
+The main issue in this code is the default statement. Only an error is returned whenever you attempt to access a custom provider. Normally the code should behave as in the "AZURE_KEY_VAULT" statement.
 
 With the original code, it is impossible to achieve Always Encrypted configuration with PowerShell and a custom/generic provider. It may be possible with a full C# or Java, but all the documentation use PowerShell.
 
@@ -54,7 +54,7 @@ private static SqlColumnEncryptionKeyStoreProvider GetProvider(string providerNa
 }
 ```
 
-- IL:
+- IL :
 <div style="font-size:0.8em">
 
 |Offset	|OpCode	|Operand|
@@ -72,13 +72,13 @@ private static SqlColumnEncryptionKeyStoreProvider GetProvider(string providerNa
 By updating the IL Code from the original DLL, the SqlServer PowerShell module doesn't allow anymore you to load this assembly.
 
 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 />
+- Update by yourself the IL code, and while saving the modified DLL Reflexil will prompt you to "Register it for verification skipping" :<br />
 ![](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:
   - Enable the CLR policy for bypass Strong Name verification
-  - Register the DLL for bypass Strong Name verification for all users
+  - Register the DLL to bypass Strong Name verification for all users
 
  Commands
 ```Cmd

Readme.md

@@ -159,7 +159,7 @@ This solution provide in order:
 
 ## Known Issues
 
-- SQL Server Management Studio cannot decrypt columns when setting "Column Encryption Setting=enabled". Or we should access the .NET assemblies loaded by the 'smss' process and register the generic provider into the SqlConnection class loaded by the process. I even don't know if this can be done (easily I mean).
+- SQL Server Management Studio cannot decrypt columns when setting "Column Encryption Setting=enabled". Or we should access the .NET assemblies loaded by the 'smss' process and register the generic provider into the SqlConnection class loaded by the process. I even don't know if this can be done (easily I mean). Nevertheless, it may be possible to update the IL code of any assembly (remove Strong Name verification for this assembly) loaded by ssms.exe to provide a static constructor (in any existing class) that would load the assembly of the generic provider ([the generic dll](bin\SQLServerAlwaysEncrypted.dll)) and create an instance of this generic provider with the right parameters to access the key, and register it. This would allow ssms.exe to decrypt columns.
 
 ![connectionstring](assets/smss_settings.png)
 
@@ -179,13 +179,12 @@ SELECT [PatientID]
 ```
 
 Output:
-<blockquote style="color:red;">
+```
 Msg 0, Level 11, State 0, Line 0<br />
 Failed to decrypt column 'SSN'.<br />
 Msg 0, Level 11, State 0, Line 0<br />
 Failed to decrypt a column encryption key. Invalid key store provider name: 'GENERIC'...
 ```
-</blockquote>
 
 
 ## Licence