diff options
author | Hans-Christoph Steiner <hans@eds.org> | 2019-11-26 20:58:54 +0100 |
---|---|---|
committer | Hans-Christoph Steiner <hans@eds.org> | 2019-11-26 21:03:19 +0100 |
commit | a3fd19302312d44257f175bded3551bc1397ced6 (patch) | |
tree | fe935d1f7925a9bbc1e7de08dcda27c4b5b56b78 /bandwidth-file-spec.txt | |
parent | c15cc8a5a869ef82f08e77c79074b892fac55932 (diff) | |
download | torspec-a3fd19302312d44257f175bded3551bc1397ced6.tar.gz torspec-a3fd19302312d44257f175bded3551bc1397ced6.zip |
fix erroneous header numbering punctuation
The clear standard is trailing "." after each numeric section. This fixes
the small handful of outliers. This makes it easy to convert these headers
to common markup formats, for example:
http://hyperpolyglot.org/lightweight-markup
Diffstat (limited to 'bandwidth-file-spec.txt')
-rw-r--r-- | bandwidth-file-spec.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/bandwidth-file-spec.txt b/bandwidth-file-spec.txt index 7564c4c..5a2954c 100644 --- a/bandwidth-file-spec.txt +++ b/bandwidth-file-spec.txt @@ -33,7 +33,7 @@ Nick Mathewson (nickm) Iain Learmonth (irl) -1.3 Outline +1.3. Outline The Tor directory protocol (dir-spec.txt [3]) sections 3.4.1 and 3.4.2, use the term bandwidth measurements, to refer to what @@ -644,7 +644,7 @@ 2.4. Implementation details -2.4.1 Writing bandwidth files atomically +2.4.1. Writing bandwidth files atomically To avoid inconsistent reads, implementations SHOULD write bandwidth files atomically. If the file is transferred from another host, it SHOULD be |