work

Author: nkolev92

designs/NuGet-CPPCLI-Support.md

@@ -84,7 +84,7 @@ Whatever the effective frameworks turn out to be, there are 2 approaches that we
 
 This would require project type changes. The project type would specify which target framework to fall back to. This likely requires fixing [5957](https://github.com/NuGet/Home/issues/5957).
 
-* Introduce a `dual compatibility` framework
+* Introduce a `dedicated dual compatibility` framework
 
 Similar to how `.NET Core` implements `.NET Standard` and supports `.NET Core` as a same family framework, we can add a framework type that's only allowed in projects, and not packages. This framework could define it's compatible as both `native` and `managed`.
 
@@ -102,9 +102,9 @@ TBD
 
 * When a package contains both `native` and `managed` assets, which ones are preferred?
 
-* Which framework changes should we adopt? Do C++/CLI projects?
+* Which frameworks are going to be supported with .NET Core C++/CLI? Will net5.0-windows be supported eventually? Asset Target Fallback becomes tricky if so.
 
-* What all frameworks are going to be supported with .NET Core C++/CLI? Will net5.0-windows be supported eventually? Asset Target Fallback becomes tricky if so.
+* Which framework changes should we adopt? Asset Target Fallback or a `dedicated dual compatibility framework`.
 
 ## Considerations