From 5c065f850c9198f02d4129b58a026a3d2d414a6a Mon Sep 17 00:00:00 2001 From: Hyuk Myeong Date: Fri, 17 Jan 2020 04:05:11 +0900 Subject: [PATCH] Fix typos (#1549) * R.37 : it callees -> its callees * ES.65 : a different part from the original paper --- CppCoreGuidelines.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index 0264d18..d75c3b3 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -9851,7 +9851,7 @@ The following should not pass code review: void my_code() { // BAD: passing pointer or reference obtained from a nonlocal smart pointer - // that could be inadvertently reset somewhere inside f or it callees + // that could be inadvertently reset somewhere inside f or its callees f(*g_p); // BAD: same reason, just passing it as a "this" pointer @@ -12315,7 +12315,7 @@ wrong results, or memory corruption. This rule is an obvious and well-known language rule, but can be hard to follow. It takes good coding style, library support, and static analysis to eliminate violations without major overhead. -This is a major part of the discussion of [C++'s resource- and type-safety model](#Stroustrup15). +This is a major part of the discussion of [C++'s model for type- and resource-safety](#Stroustrup15). **See also**: