summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTails developers <amnesia@boum.org>2015-02-20 16:20:46 +0100
committerTails developers <amnesia@boum.org>2015-02-20 16:20:46 +0100
commit5f862ff4c8f1408f9d7c903af2aac5b782b0f6fb (patch)
tree4a25d3256f390d262e25e2434db5b561da7c0a0f
parent7bc9208ed052df7900cd3eb74d7e50021484f070 (diff)
-rw-r--r--wiki/src/contribute/design/Time_syncing.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/wiki/src/contribute/design/Time_syncing.mdwn b/wiki/src/contribute/design/Time_syncing.mdwn
index 214c2d8..1ebf9f6 100644
--- a/wiki/src/contribute/design/Time_syncing.mdwn
+++ b/wiki/src/contribute/design/Time_syncing.mdwn
@@ -30,7 +30,7 @@ In short this is how time syncing is performed when Tails starts:
authority we picked (or certificates of the bridges we've
configured in bridge mode) isn't valid, so we set the system time
to the valid-after date of the certificate (in bridge mode we get
- one ceritifacte per bridge, so we set it to the highest valid-after
+ one certificate per bridge, so we set it to the highest valid-after
date we see so that all bridges' certificates are valid).
0. Set the system time to an initial "guess" based on the Tor
consensus validity period, no matter if the consensus was verifiable