Update using-cpp-interop-implicit-pinvoke.md

jkotas · web-flow · commit 3b67fbc0ff63 · 2020-01-01T20:43:42.000-08:00
Incorporate feedback from https://github.com/dotnet/coreclr/issues/659#issuecomment-558914602
diff --git a/docs/dotnet/using-cpp-interop-implicit-pinvoke.md b/docs/dotnet/using-cpp-interop-implicit-pinvoke.md
@@ -20,7 +20,7 @@ Explicit PInvoke is supported by the .NET Framework and is available in most .NE
 
 ## C++ Interop
 
-C++ Interop is recommended over explicit PInvoke because it provides better type safety, is typically less tedious to implement, is more forgiving if the unmanaged API is modified, and makes performance enhancements possible that are not possible with explicit PInvoke. However, C++ Interop is not possible if the unmanaged source code is not available.
+C++ Interop provides better type safety and it is typically less tedious to implement. However, C++ Interop is not an option if the unmanaged source code is not available or for cross-platform projects.
 
 ## C++ COM Interop
 
