Update text/0000-packages-as-optional-namespaces.md

Co-authored-by: Eric Huss <eric@huss.org>

Author: Manishearth

text/0000-packages-as-optional-namespaces.md

@@ -140,7 +140,7 @@ One thing that could mitigate `foo/bar` mapping to the potentially ambiguous `fo
 
 The `/` proposal does not require changes to Rust compiler to allow slash syntax (or whatever) to parse as a Rust path. Such changes could be made (though not with slash syntax due to parsing ambiguity, see [below](#separator-choice) for more options); this RFC is attempting to be minimal in its effects on rustc.
 
-However, the divergence between Cargo.toml and rustc syntax does indeed have a complexity cost, and may be confusing to some users. Furthermore, it increases the chances of [Dash typosquatting](#Dash typosquatting) being effective.
+However, the divergence between Cargo.toml and rustc syntax does indeed have a complexity cost, and may be confusing to some users. Furthermore, it increases the chances of [Dash typosquatting](#dash-typosquatting) being effective.
 
 Some potential mappings for `foo/bar` could be: