Merge pull request MicrosoftDocs#2587 from MicrosoftDocs/FromPublicMasterBranch

megvanhuygen · web-flow · commit 038fd90f5b1b · 2020-01-03T16:15:18.000-08:00
From public master branch
diff --git a/docs/build/vcpkg.md b/docs/build/vcpkg.md
@@ -176,7 +176,7 @@ You can modify your clone of vcpkg in any way you like. You can create multiple
 
 ## Uninstall vcpkg
 
-Just delete the directory.
+Just delete the vcpkg directory. Deleting this directory uninstalls the vcpkg distribution, and all the libraries that vcpkg has installed.
 
 ## Send feedback about vcpkg
 
diff --git a/docs/cppcx/wrl/windows-runtime-cpp-template-library-wrl.md b/docs/cppcx/wrl/windows-runtime-cpp-template-library-wrl.md
@@ -141,5 +141,5 @@ A `WeakRef` object typically represents an object whose existence is controlled
 |-|-|
 |[Key APIs by Category](key-wrl-apis-by-category.md)|Highlights the primary Windows Runtime C++ Template Library types, functions, and macros.|
 |[Reference](wrl-reference.md)|Contains reference information for the Windows Runtime C++ Template Library.|
-|[Quick Reference C++/CX)](../../cppcx/quick-reference-c-cx.md)|Briefly describes the C++/CX features that support the Windows Runtime.|
+|[Quick Reference (C++/CX)](../../cppcx/quick-reference-c-cx.md)|Briefly describes the C++/CX features that support the Windows Runtime.|
 |[Using Windows Runtime Components in Visual C++](/windows/uwp/winrt-components/walkthrough-creating-a-basic-windows-runtime-component-in-cpp-and-calling-it-from-javascript-or-csharp)|Shows how to use C++/CX to create a basic Windows Runtime component.|
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
 
