From 97716ed28af9f7b5e025ae29d8950d03ce79560e Mon Sep 17 00:00:00 2001
From: Alexander Sulfrian <alexander@sulfrian.net>
Date: Wed, 6 Jan 2016 18:35:54 +0100
Subject: [PATCH] C.168: Fixed some typos.

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

diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md
index 2e9766c..583d4f0 100644
--- a/CppCoreGuidelines.md
+++ b/CppCoreGuidelines.md
@@ -6308,18 +6308,18 @@ By itself, `cout_my_class` would be OK, but it is not usable/composabe with code
     // ...
     cout << "var = " << var << '\n';
     
-###### Note
+##### Note
 
 There are strong and vigorous conventions for the meaning most operators, such as 
 
-* comparisons (`==`, `!=`, '<', `<=`, `>`, and `>=`),
+* comparisons (`==`, `!=`, `<`, `<=`, `>`, and `>=`),
 * arithmetic operations (`+`, `-`, `*`, `/`, and `%`)
 * access operations (`.`, `->`, unary `*`, and `[]`)
 * assignment and initialization (`=`)
 
-Don't define those unconventionally and don't invent yur own names for them.
+Don't define those unconventionally and don't invent your own names for them.
 
-###### Enforcement
+##### Enforcement
 
 Tricky. Requires semantic insight.