Style fixes

Colin Robertson · web-flow · commit 447b1b97dfe5 · 2020-08-20T17:09:44.000-07:00
Update to add actual error message, make Acrolinx and i18n happier, fix Example heading, set current date, add example comments, fix code style.
diff --git a/docs/code-quality/c26409.md b/docs/code-quality/c26409.md
@@ -1,32 +1,36 @@
 ---
 title: C26409
-ms.date: 07/21/2017
+ms.date: 08/20/2020
 ms.topic: "conceptual"
 f1_keywords: ["C26409"]
 helpviewer_keywords: ["C26409"]
 ms.assetid: a3b3a229-d566-4be3-bd28-2876ccc8dc37
 ---
 # C26409 NO_NEW_DELETE
 
-Even if code is clean of calls to malloc() and free() we still suggest that you consider better options than explicit use of operators [new and delete](/cpp/cpp/new-and-delete-operators).
+> `Avoid calling new and delete explicitly, use std::make_unique<T> instead (r.11).`
 
-  **C++ Core Guidelines**:
+Even if code is clean of calls to` malloc()` and `free()`, we still suggest that you consider better options than explicit use of operators [`new` and `delete`](/cpp/cpp/new-and-delete-operators).
+
+**C++ Core Guidelines**:\
 [R.11: Avoid calling new and delete explicitly](https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#r11-avoid-calling-new-and-delete-explicitly)
 
-The ultimate fix is to start using smart pointers with appropriate factory functions, such as [std::make_unique](/cpp/standard-library/memory-functions#make_unique).
+The ultimate fix is to use smart pointers and appropriate factory functions, such as [`std::make_unique`](/cpp/standard-library/memory-functions#make_unique).
 
 ## Remarks
 
-- The checker warns on calls to any kind of operator **`new`** or **`delete`**: scalar, vector, overloaded versions (global and class-specific), as well as on placement versions. The latter case may require some clarifications on the Core Guidelines in terms of suggested fixes and may be omitted in the future.
+- The checker warns on calls to any kind of operator **`new`** or **`delete`**: scalar, vector, overloaded versions (global and class-specific), and placement versions. The placement **`new`** case may require some clarifications in the Core Guidelines for suggested fixes, and may be omitted in the future.
 
-# Example
-```cpp
+## Example
+
+This example shows C26409 is raised for explicit **`new`** and **`delete`**. Consider using smart pointer factory functions such as `std::make_unique` instead.
 
+```cpp
 void f(int i)
 {
-  int* arr = new int[i]{}; // C26409, warning is issued for all new calls
-  delete[] arr;            // C26409, warning is issued for all delete calls
-  
-  auto unique = std::make_unique<int[]>(i); // prefer using smart pointers over new and delete
+    int* arr = new int[i]{}; // C26409, warning is issued for all new calls
+    delete[] arr;            // C26409, warning is issued for all delete calls
+
+    auto unique = std::make_unique<int[]>(i); // prefer using smart pointers over new and delete
 } 
 ```
