From 5f7432b131eedcc91d027f2a175c508ba89cda1f Mon Sep 17 00:00:00 2001 From: Michael Park Date: Fri, 18 Dec 2015 15:23:59 +0000 Subject: [PATCH] C.36: Fixed a couple of typos. --- CppCoreGuidelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index 6ca3d8b..6f13c28 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -3839,7 +3839,7 @@ The standard library requires that all classes it deals with have destructors th Many have tried to devise a fool-proof scheme for dealing with failure in destructors. None have succeeded to come up with a general scheme. -This can be be a real practical problem: For example, what about a sockets that won't close? +This can be a real practical problem: For example, what about a socket that won't close? The writer of a destructor does not know why the destructor is called and cannot "refuse to act" by throwing an exception. See [discussion](#Sd-dtor). To make the problem worse, many "close/release" operations are not retryable.