From 50afe0234ce4f2f6bde7d9b0d86e926bd479f9aa Mon Sep 17 00:00:00 2001
From: boyeong-jeon <93704198+boyeong-jeon@users.noreply.github.com>
Date: Tue, 2 Jul 2024 22:19:37 +0900
Subject: [PATCH] E.16: Fix inconsistent description (#2209)

---
 CppCoreGuidelines.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md
index da7975750..8589d784b 100644
--- a/CppCoreGuidelines.md
+++ b/CppCoreGuidelines.md
@@ -16363,7 +16363,7 @@ The standard library assumes that destructors, deallocation functions (e.g., `op
 * `swap` functions must be `noexcept`.
 * Most destructors are implicitly `noexcept` by default.
 * Also, [make move operations `noexcept`](#Rc-move-noexcept).
-* If writing a type intended to be used as an exception type, ensure its copy constructor is not `noexcept`. In general we cannot mechanically enforce this, because we do not know whether a type is intended to be used as an exception type.
+* If writing a type intended to be used as an exception type, ensure its copy constructor is `noexcept`. In general we cannot mechanically enforce this, because we do not know whether a type is intended to be used as an exception type.
 * Try not to `throw` a type whose copy constructor is not `noexcept`. In general we cannot mechanically enforce this, because even `throw std::string(...)` could throw but does not in practice.
 
 ##### Enforcement