Replace (wrong) download info with branch info

After the master branch did a rename of the project folder
when migrating to dotnet core we need to also move
our added TagDefinitions to the new location of the project.

MustacheSharp.Tests/MustacheSharp.Tests.csproj

@@ -1,8 +1,8 @@
 <Project Sdk="Microsoft.NET.Sdk">
 
   <PropertyGroup>
-    <TargetFramework>netcoreapp2.1</TargetFramework>
-
+    <!-- <TargetFramework>netcoreapp2.1</TargetFramework> -->
+    <TargetFrameworks>NET45;netstandard2.0</TargetFrameworks>
     <IsPackable>false</IsPackable>
 
     <SignAssembly>true</SignAssembly>

MustacheSharp/MustacheSharp.csproj

@@ -6,7 +6,7 @@
     <SignAssembly>true</SignAssembly>
     <AssemblyOriginatorKeyFile>MustacheSharp.snk</AssemblyOriginatorKeyFile>
     <DelaySign>false</DelaySign>
-    <AssemblyName>mustache-sharp</AssemblyName>
+    <AssemblyName>MustacheSharp</AssemblyName>
     <Authors>Truncon</Authors>
     <Description>An extension of the mustache text template engine for .NET.</Description>
     <Copyright>Copyright © 2013</Copyright>

README.md

@@ -2,7 +2,9 @@
 
 An extension of the mustache text template engine for .NET.
 
-Download using NuGet: [mustache#](http://nuget.org/packages/mustache-sharp)
+## Branches
+- **feature-compare-tags**: adds additional tags like eq, lt, gt, ... as described below.
+- **master**: contains the original version forked from [jehugaleahsa/mustache-sharp](/jehugaleahsa/mustache-sharp).
 
 ## Overview
 Generating text has always been a chore. Either you're concatenating strings like a mad man or you're getting fancy with `StringBuilder`. Either way, the logic for conditionally including values or looping over a collection really obscures the intention of the code. A more declarative approach would improve your code big time. Hey, that's why server-side scripting got popular in the first place, right?