Merge pull request #1869 from mikeblome/mb-resource

PRMerger20 · web-flow · commit 9c99bf0312a4 · 2019-04-06T06:57:50.000+08:00
fixed wording that was confusing to reader
diff --git a/docs/cpp/how-to-design-for-exception-safety.md b/docs/cpp/how-to-design-for-exception-safety.md
@@ -17,7 +17,7 @@ No matter how a function handles an exception, to help guarantee that it is "exc
 
 ### Keep Resource Classes Simple
 
-When you encapsulate manual resource management in classes, use a class that does nothing else to manage each resource; otherwise, you might introduce leaks. Use [smart pointers](../cpp/smart-pointers-modern-cpp.md) when possible, as shown in the following example. This example is intentionally artificial and simplistic to highlight the differences when `shared_ptr` is used.
+When you encapsulate manual resource management in classes, use a class that does nothing except manage a single resource. By keeping the class simple, you reduce the risk of introducing resource leaks. Use [smart pointers](../cpp/smart-pointers-modern-cpp.md) when possible, as shown in the following example. This example is intentionally artificial and simplistic to highlight the differences when `shared_ptr` is used.
 
 ```cpp
 // old-style new/delete version
