Apply Tyler's suggestion

Author: eholk

docs/code-quality/c6011.md

@@ -66,7 +66,7 @@ The careless use of `malloc` and `free` leads to memory leaks and exceptions. To
 
 ## Heuristics
 
-Code analysis assumes pointers are non-null unless there is some evidence that they might be null, which is a heuristic used to reduce the number of warnings in legacy code. In the examples we've seen so far, pointers returned by `malloc` or `new` might be null because allocation might fail. Another characteristic that the analysis engine uses as evidence of nullability is if the program explicitly checks for null. This is illustrated in the following examples:
+A heuristic used to reduce the number of warnings in legacy code assumes that a pointer is non-`NULL` unless there is evidence that it is `NULL`. In the examples we've seen so far, pointers returned by `malloc` or `new` might be `NULL` because allocation might fail. Another characteristic that the analysis engine uses as evidence of nullability is if the program explicitly checks for `NULL`. This is illustrated in the following examples:
 
 ```cpp
 void f(int* n)