From 2cfc51b19e7dcd0f79ee4d69beeff42e27cdb67f Mon Sep 17 00:00:00 2001 From: Hiroshi Inoue Date: Tue, 18 Jul 2017 17:52:47 +0000 Subject: fix typos in a document; NFC llvm-svn: 308331 --- llvm/docs/CodingStandards.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'llvm/docs') diff --git a/llvm/docs/CodingStandards.rst b/llvm/docs/CodingStandards.rst index 722718bf4f1..fa41198755f 100644 --- a/llvm/docs/CodingStandards.rst +++ b/llvm/docs/CodingStandards.rst @@ -34,10 +34,10 @@ There are some conventions that are not uniformly followed in the code base (e.g. the naming convention). This is because they are relatively new, and a lot of code was written before they were put in place. Our long term goal is for the entire codebase to follow the convention, but we explicitly *do not* -want patches that do large-scale reformating of existing code. On the other +want patches that do large-scale reformatting of existing code. On the other hand, it is reasonable to rename the methods of a class if you're about to -change it in some other way. Just do the reformating as a separate commit from -the functionality change. +change it in some other way. Just do the reformatting as a separate commit +from the functionality change. The ultimate goal of these guidelines is to increase the readability and maintainability of our common source base. If you have suggestions for topics to -- cgit v1.2.3