aboutsummaryrefslogtreecommitdiffstats
path: root/proposals
diff options
context:
space:
mode:
authorBret Comnes <bcomnes@gmail.com>2018-03-23 11:06:02 -0700
committerGitHub <noreply@github.com>2018-03-23 11:06:02 -0700
commit9b60e7f06c3ae2f7d409c6caa6908ff3589411bf (patch)
tree6ce136ddf2d9916e5fb77b3879498c88f794ce66 /proposals
parent0723ee3bc70067190cbe97d7d4d686b4bba651a1 (diff)
downloaddat-deps-9b60e7f06c3ae2f7d409c6caa6908ff3589411bf.tar.gz
dat-deps-9b60e7f06c3ae2f7d409c6caa6908ff3589411bf.zip
Fix hash link
Diffstat (limited to 'proposals')
-rw-r--r--proposals/0002-hypercore.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/proposals/0002-hypercore.md b/proposals/0002-hypercore.md
index b01ea0d..a6a560e 100644
--- a/proposals/0002-hypercore.md
+++ b/proposals/0002-hypercore.md
@@ -321,7 +321,7 @@ IPFS is designed for immutable hash-addressed content, but it provides a mechani
# Unresolved questions
[unresolved]: #unresolved-questions
-- Is there a potential "branch resolution" protocol which could remove the [linear history requirement](#linear-history-requirement) and therefore enable users to share private keys freely between their devices? Explaining the risks of branches to users is difficult. (This is being explored.)
+- Is there a potential "branch resolution" protocol which could remove the [linear history requirement](#the-linear-history-requirement) and therefore enable users to share private keys freely between their devices? Explaining the risks of branches to users is difficult. (This is being explored.)
# Changelog