commit bfaf4c27e7ebd322b6451ddb40710d84a88c7454 Author: Roger Dingledine <arma@torproject.org> Date: Mon Nov 16 15:33:35 2020 -0500 fix typos; more robust links between specs --- control-spec.txt | 8 +++++--- dir-spec.txt | 3 +-- path-spec.txt | 2 +- 3 files changed, 7 insertions(+), 6 deletions(-) diff --git a/control-spec.txt b/control-spec.txt index 12dd1a7..72d3195 100644 --- a/control-spec.txt +++ b/control-spec.txt @@ -3605,7 +3605,8 @@ configuration option. Tor accepts relative and full path. Message = The log message that the PT sends back to the tor parent process minus the "LOG" string prefix. Formatted as - specified in pt-spec.txt section 3.3.4. + specified in pt-spec.txt section "3.3.4. Pluggable + Transport Log Message". This event is triggered when tor receives a log message from the PT. @@ -3627,11 +3628,12 @@ Program = The program path as defined in the *TransportPlugin configuration option. Tor accepts relative and full path. - Transport = This value indicate a hint on what the PT is such has the + Transport = This value indicate a hint on what the PT is such as the name or the protocol used for instance. Message = The status message that the PT sends back to the tor parent process minus the "STATUS" string prefix. Formatted as - specified in pt-spec.txt section 3.3.5. + specified in pt-spec.txt section "3.3.5 Pluggable + Transport Status Message". This event is triggered when tor receives a log message from the PT. diff --git a/dir-spec.txt b/dir-spec.txt index a29d86a..eed7ccf 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -1782,8 +1782,7 @@ (Note that because of propagation delays, clients and relays may see consensus documents that are up to `DistSeconds` - earlier than this this time, and should not warn about - them.) + earlier than this time, and should not warn about them.) See section 1.4 for voting timeline information. diff --git a/path-spec.txt b/path-spec.txt index d728131..483e37d 100644 --- a/path-spec.txt +++ b/path-spec.txt @@ -124,7 +124,7 @@ of their choices. Here, "enough" directory information is defined as: * Having a consensus that's been valid at some point in the - last REASONABLY_LIVE_TIME interval (24 hourts). + last REASONABLY_LIVE_TIME interval (24 hours). * Having enough descriptors that we could build at least some fraction F of all bandwidth-weighted paths, without taking