From dfde58db6b4ca0b406b872d7b049efbe07d7a0fe Mon Sep 17 00:00:00 2001
From: "Chelsea H. Komlo" <chelsea.komlo@gmail.com>
Date: Wed, 21 Dec 2016 17:07:57 -0500
Subject: [PATCH] check-spaces is run as part of make check

---
 doc/HACKING/CodingStandards.md | 2 --
 1 file changed, 2 deletions(-)

diff --git a/doc/HACKING/CodingStandards.md b/doc/HACKING/CodingStandards.md
index 9932c77353..c7787a72cc 100644
--- a/doc/HACKING/CodingStandards.md
+++ b/doc/HACKING/CodingStandards.md
@@ -4,7 +4,6 @@ Coding conventions for Tor
 tl;dr:
 
    - Run configure with `--enable-fatal-warnings`
-   - Run `make check-spaces` to catch whitespace errors
    - Document your functions
    - Write unit tests
    - Run `make test-full` to test against all unit and integration tests.
@@ -24,7 +23,6 @@ preference)
 Did you remember...
 
    - To build your code while configured with `--enable-fatal-warnings`?
-   - To run `make check-spaces` on your code?
    - To run `make check-docs` to see whether all new options are on
      the manpage?
    - To write unit tests, as possible?