docs(readme): update verbiage

Author: MarkPieszak

README.md

@@ -4,24 +4,22 @@
 
 > Updated to the latest Angular 6.x
 
-> Note ServerTransferModule still in the works - fix coming soon
-
 <p align="center">
-    <img src="./docs/architecture.png" alt="ASP.NET Core 2.0 Angular 5+ Starter" title="ASP.NET Core 2.0 Angular 5+ Starter">
+    <img src="./docs/architecture.png" alt="ASP.NET Core 2.0 Angular 6+ Starter" title="ASP.NET Core 2.0 Angular 6+ Starter">
 </p>
 
-### Harness the power of Angular 5+, ASP.NET Core 2.0, now with SEO !
+### Harness the power of Angular 6+, ASP.NET Core 2.0, now with SEO !
 
 Angular SEO in action:
 
 <p align="center">
-  <img src="./docs/angular2-seo.png" alt="ASP.NET Core Angular5 SEO" title="ASP.NET Core Angular5 SEO">
+  <img src="./docs/angular2-seo.png" alt="ASP.NET Core Angular6 SEO" title="ASP.NET Core Angular6 SEO">
 </p>
 
 ### What is this repo? Live Demo here: http://aspnetcore-angular2-universal.azurewebsites.net
 
 This repository is maintained by [Angular](https://github.com/angular/angular) and is meant to be an advanced starter 
-for both ASP.NET Core 2.0 using Angular 5.0+, not only for the client-side, but to be rendered on the server for instant 
+for both ASP.NET Core 2.0 using Angular 6.0+, not only for the client-side, but to be rendered on the server for instant 
 application paints (Note: If you don't need SSR [read here](#faq) on how to disable it).
 
 This is meant to be a Feature-Rich Starter application containing all of the latest technologies, best build systems available, and include many real-world examples and libraries needed in todays Single Page Applications (SPAs).
@@ -47,15 +45,15 @@ This utilizes all the latest standards, no gulp, no bower, no typings, no manual
 
 > These are just some of the features found in this starter!
 
-- ASP.NET 2.0 - VS2017 15.3 support now!
+- ASP.NET 2.1 - VS2017 support now!
   - Azure delpoyment straight from VS2017
   - Built in docker support through VS2017
   - RestAPI (WebAPI) integration
   - SQL Database CRUD demo
   - Swagger WebAPI documentation when running in development mode 
   - SignalR Chat demo! (Thanks to [@hakonamatata](https://github.com/hakonamatata))
 
-- **Angular 5.0.0** :
+- **Angular 6.0.0** :
   - (Minimal) Angular-CLI integration 
     - This is to be used mainly for Generating Components/Services/etc.
     - Usage examples: 
@@ -69,7 +67,7 @@ This utilizes all the latest standards, no gulp, no bower, no typings, no manual
     - Can be easily replaced with bootstrap4 (3 is provided for browser support)
     - Bootstrap using SCSS / SASS for easy theming / styling!
 
-- **Webpack build system (Webpack 2)**
+- **Webpack build system (Webpack 4)**
   - HMR : Hot Module Reloading/Replacement 
   - Production builds w/ AoT Compilation
 
@@ -87,7 +85,7 @@ This utilizes all the latest standards, no gulp, no bower, no typings, no manual
 
 - **Azure**
   - Microsoft Application Insights setup (for MVC & Web API routing)
-  - Client-side Angular2 Application Insights integration
+  - Client-side Angular Application Insights integration
     - If you're using Azure simply install `npm i -S @markpieszak/ng-application-insights` as a dependencies.
     - Note: Make sure only the Browser makes these calls ([usage info here](https://github.com/MarkPieszak/angular-application-insights/blob/master/README.md#usage))
     - More information here: - https://github.com/MarkPieszak/angular-application-insights
@@ -97,18 +95,16 @@ This utilizes all the latest standards, no gulp, no bower, no typings, no manual
         instrumentationKey: 'Your-Application-Insights-instrumentationKey'
       })
     ```
-  
-
-> Looking for the older 2.x branch? Go [here](https://github.com/MarkPieszak/aspnetcore-angular2-universal/tree/old-2.x-universal-branch)
+ 
 
 ----
 
 ----
 
 # Getting Started?
 
-- **Make sure you have at least Node 6.x or higher (w/ npm 3+) installed!**  
-- **This repository uses ASP.Net Core 2.0, which has a hard requirement on .NET Core Runtime 2.0.0 and .NET Core SDK 2.0.0. Please install these items from [here](https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.0.0-download.md)**
+- **Make sure you have at least Node 8.11.1 or higher (w/ npm 5+) installed!**  
+- **This repository uses ASP.Net Core 2.1, which has a hard requirement on .NET Core Runtime 2.1 and .NET Core SDK 2.1. Please install these items from [here](https://blogs.msdn.microsoft.com/dotnet/2018/05/30/announcing-net-core-2-1/?WT.mc_id=blog-twitter-timheuer)**
 
 
 ### Visual Studio 2017
@@ -143,8 +139,9 @@ export ASPNETCORE_ENVIRONMENT=Development
 
 # Upcoming Features:
 
-- Fix HttpTransferCacheModule & ServerTransferModule to work with aspnet-engine
-- ~~Update to use npm [ngAspnetCoreEngine](https://github.com/angular/universal/pull/682) (still need to tweak a few things there)~~
+- Clean API / structure / simplify application
+- Refactor to latest RxJs pipeable syntax
+- Attempt to integrate with Angular-CLI fully
 
 ----
 
@@ -296,7 +293,7 @@ Take a look at the `_Layout.cshtml` file for example, notice how we let .NET han
     <head>
         <base href="/" />
         <!-- Title will be the one you set in your Angular application -->
-        <title>@ViewData["Title"] - AspNET.Core Angular 5.0.0 (+) starter</title>
+        <title>@ViewData["Title"] - AspNET.Core Angular 6.0.0 (+) starter</title>
 
         <meta charset="utf-8" />
         <meta name="viewport" content="width=device-width, initial-scale=1.0" />
@@ -335,9 +332,9 @@ Well now, your Client-side Angular will take over, and you'll have a fully funct
 
 # "Gotchas"
 
-- This repository uses ASP.Net Core 2.0, which has a hard requirement on .NET Core Runtime 2.0.0 and .NET Core SDK 2.0.0. Please install these items from [here](https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.0.0-download.md)
+- This repository uses ASP.Net Core 2.1, which has a hard requirement on .NET Core Runtime 2.1 and .NET Core SDK 2.1. Please install these items from [here](https://blogs.msdn.microsoft.com/dotnet/2018/05/30/announcing-net-core-2-1/?WT.mc_id=blog-twitter-timheuer)
 
-> When building components in Angular 5 there are a few things to keep in mind.
+> When building components in Angular 6 there are a few things to keep in mind.
 
  - Make sure you provide Absolute URLs when calling any APIs. (The server can't understand relative paths, so `/api/whatever` will fail).