diff --git a/Project-Status.md b/Project-Status.md
index d7e618e..3609414 100644
--- a/Project-Status.md
+++ b/Project-Status.md
@@ -6,16 +6,14 @@ Refer to project scope [here](https://github.com/PowerShell/Win32-OpenSSH/wiki/P
  - Visual Studio 2015 solution to build OpenSSH for Windows.
  - Secure architecture for Windows: OpenSSH server side architecture is altered for Windows adhering to its security principles. This is done with minimal impact to overall source layout. 
  - Secure ssh-agent: A different version of agent is authored for Windows to fit Windows security model and enable a Single Sign-On experience. 
+ - VT100/ANSI TTY and PTY: Rewritten client side ANSI parser to accurately interpret and render VT100 stream on Windows console. Server side VT100 PTY that will support rich Windows console applications. 
 
-#### Work in progress (ETA - 9/23)
- - Improving Terminal experience: Interactive remote shell experience in the current version of this project is impacted by a bunch of [issues](https://github.com/PowerShell/Win32-OpenSSH/labels/Area-Terminal%20experience). Following is being done to address these:
-    - Rewriting client side ANSI parser to enable ssh client to accurately interpret and render VT100 (mapping VT100 to Windows console calls). 
-    - Enable ssh server to support rich Windows console application over remote sessions (mapping Windows console calls to VT100)
-    - Validating the following key strokes behavior on multiple SSH targets - CR+LF, BS, Tab and Arrow Keys. 
+#### Work in progress
+ - Unicode support in Windows: Windows APIs are typically UTF-16 based while on Unix, its UTF-8. Details [here](https://github.com/PowerShell/Win32-OpenSSH/issues/319).  
+ - POSIX File API support in Windows: Currently SFTP and SCP have significant Windows differentiated code. This enables effective Unix based code usage on Windows.  Tracked [here](https://github.com/PowerShell/Win32-OpenSSH/issues/320).
 
 #### Work in pipeline
- - Unicode support in Windows: Windows APIs are typically UTF-16 based while on Unix, its UTF-8. Need to figure out a workable solution that would support both models. Details [here](https://github.com/PowerShell/Win32-OpenSSH/issues/319).  
- - POSIX File API support in Windows: Currently SFTP and SCP have significant Windows differentiated code. This enables effective Unix based code usage on Windows.  Tracked [here](https://github.com/PowerShell/Win32-OpenSSH/issues/320).
+ - Enable PTY on nano server. 
  - Code cleanup and refactoring: In entire project specific logic has been ifdef'ed and spread out at various places in the project in an attempt to achieve a workable solution on Windows. These need to be cleaned up and refactored as per OpenBSD's coding guidelines in order to get to an acceptable state. Tracked [here] (https://github.com/PowerShell/Win32-OpenSSH/issues?q=is%3Aopen+is%3Aissue+label%3A%22Area-Code+Cleanup%22).
  - Syncing Win32 fork with the latest changes from OpenSSH main repo. Tracked [here] (https://github.com/PowerShell/Win32-OpenSSH/issues/328).
  - SAL annotate Win32 specific code. Run static analysis.Tracked [here] (https://github.com/PowerShell/Win32-OpenSSH/issues/329).