From 37071453cbece188376b4eb03bc58c13ecf98916 Mon Sep 17 00:00:00 2001
From: Andreas Scherer <andreas_scherer@alice.de>
Date: Sun, 18 Oct 2015 11:17:07 +0200
Subject: [PATCH] Consistent Enforcement paragraphs.

---
 CppCoreGuidelines.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md
index 4dab763..206957c 100644
--- a/CppCoreGuidelines.md
+++ b/CppCoreGuidelines.md
@@ -4596,7 +4596,7 @@ Prefer copy semantics unless you are building a "smart pointer". Value semantics
 
 ##### Enforcement
 
-(Not enforceable).
+(Not enforceable)
 
 ### <a name="Rc-copy-self"></a> C.62: Make copy assignment safe for self-assignment
 
@@ -4728,7 +4728,7 @@ Unless there is an exceptionally strong reason not to, make `x = std::move(y); y
 
 ##### Enforcement
 
-(Not enforceable) look for assignments to members in the move operation. If there is a default constructor, compare those assignments to the initializations in the default constructor.
+(Not enforceable) Look for assignments to members in the move operation. If there is a default constructor, compare those assignments to the initializations in the default constructor.
 
 ### <a name="Rc-move-self"></a> C.65: Make move assignment safe for self-assignment