aboutsummaryrefslogtreecommitdiff
path: root/spec/guard-spec/algorithm.md
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2023-11-09 21:06:15 -0500
committerNick Mathewson <nickm@torproject.org>2023-11-09 21:06:15 -0500
commitdb5400a93658fc6fbf323d8ddccef988cd9cf508 (patch)
tree6e125dcea8de94b01d540e7789b7e40989c4b48f /spec/guard-spec/algorithm.md
parentbd2260419ce5981778943489fc4fc057251c5bdf (diff)
parentf275aa9f638ddef1f83006260ac27c609a426a45 (diff)
downloadtorspec-db5400a93658fc6fbf323d8ddccef988cd9cf508.tar.gz
torspec-db5400a93658fc6fbf323d8ddccef988cd9cf508.zip
Merge remote-tracking branch 'origin/mr/220'
Diffstat (limited to 'spec/guard-spec/algorithm.md')
-rw-r--r--spec/guard-spec/algorithm.md4
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