aboutsummaryrefslogtreecommitdiff
path: root/design/24301-versioned-go.md
diff options
context:
space:
mode:
Diffstat (limited to 'design/24301-versioned-go.md')
-rw-r--r--design/24301-versioned-go.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/design/24301-versioned-go.md b/design/24301-versioned-go.md
index 7b3ee49..31271c5 100644
--- a/design/24301-versioned-go.md
+++ b/design/24301-versioned-go.md
@@ -94,7 +94,7 @@ I propose to add versioning to Go using the following approach.
unless the module's documentation clearly states exceptions.
5. Record each module's path and dependency requirements in a
- [`go.mod` file](XXX) stored in the root of the module's file tree.
+ `go.mod` file stored in the root of the module's file tree.
6. To decide which module versions to use in a given build,
apply [minimal version selection](https://research.swtch.com/vgo-mvs):
@@ -108,7 +108,7 @@ I propose to add versioning to Go using the following approach.
Second, it never chooses a module version not listed in some `go.mod` file
involved in the build: new versions are not incorporated
simply because they have been published.
- The second property produces [high-fidelity builds](XXX)
+ The second property produces high-fidelity builds
and makes sure that upgrades only happen when
developers request them, never unexpectedly.