fix links

go101 · May 28, 2019 · d41195b · d41195b
1 parent 18fb2b2
commit d41195b
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/README-v9.1.md b/README-v9.1.md
@@ -1,7 +1,7 @@
 # A proposal to support read-only and practical immutable values in Go
 
 _Comparing to the last revision v9, this version forbids passing writer values as reader arguments (including receiver arguments),
-to avoid [the problem mentioned in v9](README-v9.md#the-problem-when-reader-parameters-in-a-library-package-changed-to-writers)._
+to avoid [the problem mentioned in v9](README-v9.0.md#the-problem-when-reader-parameters-in-a-library-package-changed-to-writers)._
 
 This revision is a little Go 1 incompatible, for it needs a new keyword `final`.
 
@@ -527,7 +527,7 @@ t:reader.M()
 T:reader.M(t:reader)
 ```
 
-Note, to avoid [the problem mentioned in v9](README-v9.md#the-problem-when-reader-parameters-in-a-library-package-changed-to-writers), the following method/function calls are invalid:
+Note, to avoid [the problem mentioned in v9](README-v9.0.md#the-problem-when-reader-parameters-in-a-library-package-changed-to-writers), the following method/function calls are invalid:
 ```
 var t T
 t.M()

diff --git a/README-v9.a.md b/README-v9.a.md
@@ -74,7 +74,7 @@ The following two rules stand if they stand without considering value roles.
   The conversion results can be assigned to reader values or bound to read-only values.
   (About why writer or writable values can't be implicitly
   converted to reader or read-only values, please read
-  [the problem mentioned in v9](README-v9.md#the-problem-when-reader-parameters-in-a-library-package-changed-to-writers).)
+  [the problem mentioned in v9](README-v9.0.md#the-problem-when-reader-parameters-in-a-library-package-changed-to-writers).)
 * Writer or writable values can be assigned to writer or writable values.
 
 Values of no-references types have adaptive roles when they are used as R-values (right-hand-side values). In other words,