aboutsummaryrefslogtreecommitdiff
path: root/spec/guard-spec/appendices.md
diff options
context:
space:
mode:
Diffstat (limited to 'spec/guard-spec/appendices.md')
-rw-r--r--spec/guard-spec/appendices.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/spec/guard-spec/appendices.md b/spec/guard-spec/appendices.md
index 612ff4c..34368ad 100644
--- a/spec/guard-spec/appendices.md
+++ b/spec/guard-spec/appendices.md
@@ -11,7 +11,7 @@ CNS-1314637, CNS-1526306, CNS-1619454, and CNS-1640548.
<a id="guard-spec.txt-A.1"></a>
-## Parameters with suggested values. [Section:PARAM_VALS]
+## Parameters with suggested values. \[Section:PARAM_VALS\]
(All suggested values chosen arbitrarily)
@@ -80,7 +80,7 @@ CNS-1314637, CNS-1526306, CNS-1619454, and CNS-1640548.
<a id="guard-spec.txt-A.2"></a>
-## Random values [Section:RANDOM]
+## Random values \[Section:RANDOM\]
Frequently, we want to randomize the expiration time of something
so that it's not easy for an observer to match it to its start
@@ -92,7 +92,7 @@ the past, chosen uniformly at random.
<a id="guard-spec.txt-A.3"></a>
-## Why not a sliding scale of primaryness? [Section:CVP]
+## Why not a sliding scale of primaryness? \[Section:CVP\]
At one meeting, I floated the idea of having "primaryness" be a
continuous variable rather than a boolean.
@@ -102,7 +102,7 @@ how it might work.
To begin with: being "primary" gives it a few different traits:
-1) We retry primary guards more frequently. [Section:RETRYING]
+1. We retry primary guards more frequently. \[Section:RETRYING\]
```text
2) We don't even _try_ building circuits through