Update use-cases to include working remotely. (microsoft#3873)

This is the first usecase that came to my mind. This is what most people use screen and tmux for besides multiplexing.

docs/reference/use-cases.md

@@ -39,6 +39,7 @@ This document highlights some use cases that Visual Studio Live Share is already
     - [Classroom Lectures](#classroom-lectures)
 - [Code Reviews](#code-reviews)
 - [Technical Interviews](#technical-interviews)
+- [Working Remotely](#working-remotely)
 
 ## Quick assistance
 
@@ -139,6 +140,10 @@ When interviewing candidates for a developer position, it can often be helpful t
 
 Additionally, real-world development is more than simply writing code. Because Live Share also supports shared debugging, tasks and terminals, it allows interviewers to observe candidates while diagnosing an issue, and provide them the appropriate tools needed to solve it (e.g. step debug, run tests). Since all context is remoted from the host's machine, candidates can quickly jump into the "interview environment" without needing to setup their machine (beyond installing Live Share). Teams could then maintain a repository of shared interviewing apps (or use their actual product codebase), that could be cloned and shared with candidates, by simply sending them the session URL before each interview.
 
+## Working Remotely
+
+Work from home without having to keep your home development machines tool chain in sync with your works. Quickly finish of that line of code from home without needing push from work, clone down the repo at home and find the exact line you were working on. Connect on a light weight laptop to your heavy weight work machine.
+
 ## See also
 
 - [Language and platform support](../reference/platform-support.md)