Merge pull request MicrosoftDocs#3054 from MicrosoftDocs/master

Taojunshen · web-flow · commit 1839405b9703 · 2020-08-19T01:40:05.000+08:00
8/18/2020 AM Publish
diff --git a/docs/build/reference/creating-a-makefile-project.md b/docs/build/reference/creating-a-makefile-project.md
@@ -98,6 +98,6 @@ The next time you open your makefile project in the Visual Studio development en
 
 [Using IntelliSense](/visualstudio/ide/using-intellisense)<br>
 [NMAKE Reference](nmake-reference.md)<br>
-[How to: Create a C++ Project from Existing Code](../how-to-create-a-cpp-project-from-existing-code.md)
+[How to: Create a C++ Project from Existing Code](../how-to-create-a-cpp-project-from-existing-code.md)<br>
 [Special Characters in a Makefile](special-characters-in-a-makefile.md)<br/>
 [Contents of a Makefile](contents-of-a-makefile.md)<br/>
diff --git a/docs/code-quality/c26405.md b/docs/code-quality/c26405.md
@@ -8,7 +8,7 @@ ms.assetid: 2034d961-3ec5-4184-bbef-aa792e4c03c0
 ---
 # C26405  DONT_ASSIGN_TO_VALID
 
-If an owner pointer already points to a valid memory buffer, it must not be assigned to another value without releasing its current resource first. Such assignment may lead to a resource leak even if the resource address is copied into some raw pointer (because raw pointers shouldn’t release resources).
+If an owner pointer already points to a valid memory buffer, it must not be assigned to another value without releasing its current resource first. Such assignment may lead to a resource leak even if the resource address is copied into some raw pointer (because raw pointers shouldn’t release resources). For more information, see the [C++ Core Guidelines](https://github.com/isocpp/CppCoreGuidelines/blob/master/CppCoreGuidelines.md#r3-a-raw-pointer-a-t-is-non-owning).
 
 ## Example 1: Overwriting an owner in a loop
 
