diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md
index 8e4e443..d434dbc 100644
--- a/CppCoreGuidelines.md
+++ b/CppCoreGuidelines.md
@@ -11715,6 +11715,7 @@ static nefarious n;       // oops, any destructor exception can't be caught
 ```
 void test() {
     std::array<nefarious, 10> arr; // this line can std::terminate(!)
+}
 ```
 
 The behavior of arrays is undefined in the presence of destructors that throw because there is no reasonable rollback behavior that could ever be devised. Just think: What code can the compiler generate for constructing an `arr` where, if the fourth object's constructor throws, the code has to give up and in its cleanup mode tries to call the destructors of the already-constructed objects... and one or more of those destructors throws? There is no satisfactory answer.