aboutsummaryrefslogtreecommitdiff
path: root/doc/HACKING/CodingStandards.md
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2015-11-05 09:53:05 -0500
committerNick Mathewson <nickm@torproject.org>2015-11-05 09:53:05 -0500
commit5a370618859573ed1eb5dabbe0ed2e773a579817 (patch)
tree1c107251a6dba238c8fb03490d9f692a156d344e /doc/HACKING/CodingStandards.md
parent43ce4626f1c23f723a3007e91cfb1ed5f8a75712 (diff)
downloadtor-5a370618859573ed1eb5dabbe0ed2e773a579817.tar.gz
tor-5a370618859573ed1eb5dabbe0ed2e773a579817.zip
Delete trailing whitespace in md files
Diffstat (limited to 'doc/HACKING/CodingStandards.md')
-rw-r--r--doc/HACKING/CodingStandards.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/HACKING/CodingStandards.md b/doc/HACKING/CodingStandards.md
index f7541d71dd..d2fc784efb 100644
--- a/doc/HACKING/CodingStandards.md
+++ b/doc/HACKING/CodingStandards.md
@@ -81,7 +81,7 @@ in changes to make a draft changelog, and clear the directory. We'll
then edit the draft changelog into a nice readable format.
What needs a changes file?
-
+
* A not-exhaustive list: Anything that might change user-visible
behavior. Anything that changes internals, documentation, or the build
system enough that somebody could notice. Big or interesting code
@@ -89,7 +89,7 @@ What needs a changes file?
did that happen, and/or why did we do that" 6 months down the line.
Why use changes files instead of Git commit messages?
-
+
* Git commit messages are written for developers, not users, and they
are nigh-impossible to revise after the fact.
@@ -151,7 +151,7 @@ Functions not to write
----------------------
Try to never hand-write new code to parse or generate binary
-formats. Instead, use trunnel if at all possible. See
+formats. Instead, use trunnel if at all possible. See
https://gitweb.torproject.org/trunnel.git/tree