From a67f8d3c2780f67aca56a80c5976f3aae3294f6e Mon Sep 17 00:00:00 2001 From: Marat Tanalin Date: Mon, 1 Feb 2016 19:38:31 +0300 Subject: [PATCH] Typos wil => will; developemnt => development. --- CppCoreGuidelines.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CppCoreGuidelines.md b/CppCoreGuidelines.md index f5bd1b3..1650877 100644 --- a/CppCoreGuidelines.md +++ b/CppCoreGuidelines.md @@ -6946,8 +6946,8 @@ A major class of exception is legacy code, especially code that must remain comp The fact that there are billions of lines of code that violate this rule against owning `T*`s cannot be ignored. We'd love to see program transformation tools turning 20-year-old "legacy" code into shiny modern code, we encourage the development, deploymenta and use of such tools, -we hope the guidelines wil help the development of such tools, -and we even contributed (and contribute) to the research and developemnt in this area. +we hope the guidelines will help the development of such tools, +and we even contributed (and contribute) to the research and development in this area. However, it will take time: "legacy code" is generated faster than we can renovate old code, and so it will be for a few years. This code cannot all be rewritten (ever assuming good code transformation software), especially not soon.