diff options
| author | Jim Newsome <jnewsome@torproject.org> | 2023-11-09 11:05:05 -0600 |
|---|---|---|
| committer | Jim Newsome <jnewsome@torproject.org> | 2023-11-09 18:45:20 -0600 |
| commit | b74a68361735b4a7c60ed395f417d22914986ae2 (patch) | |
| tree | 70505487c7ef84aa0ad1bb7f35be9dfbcb41617d /spec/guard-spec | |
| parent | 72722037eed69e1a05d204c62ed9629f5b571b85 (diff) | |
| download | torspec-b74a68361735b4a7c60ed395f417d22914986ae2.tar.gz torspec-b74a68361735b4a7c60ed395f417d22914986ae2.zip | |
Escape brackets that aren't meant to be reference-links
Diffstat (limited to 'spec/guard-spec')
| -rw-r--r-- | spec/guard-spec/algorithm.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/spec/guard-spec/algorithm.md b/spec/guard-spec/algorithm.md index 1db72f5..ba1c725 100644 --- a/spec/guard-spec/algorithm.md +++ b/spec/guard-spec/algorithm.md @@ -407,11 +407,11 @@ When we want to build a circuit, and we need to pick a guard: When selecting a guard according to this approach, its circuit is `<usable_on_completion>`. - [Note: We do not use {is_pending} on primary guards, since we + \[Note: We do not use {is_pending} on primary guards, since we are willing to try to build multiple circuits through them before we know for sure whether they work, and since we will not use any non-primary guards until we are sure that the - primary guards are all down. (XX is this good?)] + primary guards are all down. (XX is this good?)\] * Otherwise, if the ordered intersection of {CONFIRMED_GUARDS} and {USABLE_FILTERED_GUARDS} is nonempty, return the first |