Update documentation

CONTRIBUTING.md

@@ -6,7 +6,7 @@ A developer should be able to quickly and easily add features, pages, and have a
 
 That's why many of the guidelines of this document are obvious and serve only one purpose: **Simplicity.**
 
-Also remeber that the Pull Requests must be done aganist the **[dev branch](https://github.com/Microsoft/WindowsTemplateStudio/tree/dev)**.
+Also remember that the Pull Requests must be done aganist the **[dev branch](https://github.com/Microsoft/WindowsTemplateStudio/tree/dev)**.
 
 ## Before you begin
 

README.md

@@ -34,8 +34,8 @@ I need an app that uses MVVM Light, uses master detail, can suspend and resume,
 
 Windows Template Studio approaches UWP app creation using the following four attribute sets:
 
-* **Project type**: First, how do you want your app's UI navigation to behave? We currently support three project types: *basic*, *[navigation pane](docs/projectTypes/navigationpane.md)*, and *pivot and tabs*
-* **App framework**: Next, what coding pattern do you want to use in your project, we currently support three common patterns: *code behind*, *basic MVVM*, and *[MVVM Light](http://www.mvvmlight.net/)*
+* **Project type**: First, how do you want your app's UI navigation to behave? We currently support three project types: *basic*, *[navigation pane](docs/projectTypes/navigationpane.md)*, and *pivot and tabs*.
+* **App framework**: Next, what coding pattern do you want to use in your project, we currently support three common patterns: *code behind*, *basic MVVM*, *[MVVM Light](http://www.mvvmlight.net/)*, and *[CaliburnMicro](https://caliburnmicro.com/)*.
 * **App pages**: To accelerate app creation, we provide a number of app page templates that you can use to add common UI pages into your new app. We currently include page templates from the *blank page* to the common layouts (*e.g., master/detail, tabbed, web view*) to pages that implement common patterns (*e.g., [app settings](docs/pages/settings.md), map control*). Using the wizard, add as many of the pages as you need, providing a name for each one, and we'll generate them for you.
 * **Windows 10 features**: Lastly, you specify which UWP capabilities you want to use in your app, and we'll build out the framework for the features into your app, tagging 'TODO' items. Currently supported features cover application lifecycle (*settings storage, suspend and resume*), background tasks, and user interaction (*app notifications, Live tiles, and Azure Notification Hub*).
 
@@ -51,7 +51,7 @@ Once you select the attributes you want your new UWP app to have, you can quickl
 
 ## Known issues
 
-None Currently
+* You can't have side-by-side versions (nightly/pre-release/release) of WindowsTemplateStudio VSPackage into a single instance of Visual Studio.
 
 ## Feedback, Requests and Roadmap
 
@@ -72,7 +72,7 @@ Do you want to contribute? We would love to have you help out.  Here are our [co
 1. Generated templates once generated, must be able to be compiled and run.
 1. Generated templates should work on all device families.
 1. Templates should have comments to aid developers.  This includes links to signup pages for keys, MSDN, blogs and how-to's.  All guidance provide should be validated from either the framework/SDK/library’s creator.
-1. All features will be supported for two most recent RTM Windows 10 Updates. Those supported releases are Windows 10 Anniversary Update and Windows 10 Creators Update.
+1. All features will be supported for two most recent RTM Windows 10 Updates. Those supported releases are Windows 10 Creators Update and Windows 10 Fall Creators Update.
 1. Templates released in production will try to adhere to the design language used in the current release of Windows 10.
 1. Code should follow [.NET Core coding style](https://github.com/dotnet/corefx/blob/master/Documentation/coding-guidelines/coding-style.md)