diff --git a/README.md b/README.md
index db8067d..381fa3b 100644
--- a/README.md
+++ b/README.md
@@ -4,7 +4,9 @@ There once was a little boy named cmd.exe and a little girl named bash... Window
 
 ## Executing .exe from bash
 
-As of August 22, 2016 Windows 10 bash has no way to execute exe applications from the command line. If you wish to run an exe app from your current working directory in bash you must exit, cd into your former location, run your exe and then start bash up again. This is annoying AF and today we fix this. What if the process could be automated and allow for the pseudo-execution of exe in bash powered by cmd.exe?
+> **NOTE:** WSL in Windows 10 Creators Update (version 1703) can natively launch Windows programs from bash. You can use `bashex` if you want to use WSL on Windows 10 Anniversary Update (version 1607).
+
+The initial versions of Windows Subsystem for Linux (WSL) had no way to execute `.exe` applications from the bash command line. If you wish to run an exe app from your current working directory in bash you must exit, cd into your former location, run your exe and then start bash up again. This was annoying and this project was intended to fix it. 
 
 ## Setup
 
@@ -36,4 +38,4 @@ If you decide to contribute to bashex be careful using the cmdlet when you are i
 
 Because of how Powershell interacts with cmd.exe, PS does not support bashex @ this time. If it is found to be beneficial this functionality can easily be added with the creation of a bashex.ps1 file. 
 
-In addition, do to the security restrictions of powershell,if a bashex.ps1 port was made it would need to be launched with '.\bashex'. This is because you cannot launch a powershell script without specifying the directory of the script (this is in order to prevent malicious overrides of commonly used cmdlerts - http://superuser.com/a/695624).
\ No newline at end of file
+In addition, do to the security restrictions of powershell,if a bashex.ps1 port was made it would need to be launched with '.\bashex'. This is because you cannot launch a powershell script without specifying the directory of the script (this is in order to prevent malicious overrides of commonly used cmdlerts - http://superuser.com/a/695624).