diff --git a/MinorReleases.md b/MinorReleases.md
index d7bcb661..c1c78f89 100644
--- a/MinorReleases.md
+++ b/MinorReleases.md
@@ -1,4 +1,4 @@
-Our default decision should always be to not backport, but fixes for **security issues**, **serious problems with no workaround**, and **documentation fixes** are backported to the most recent two release branches, if applicable to that branch. (for example, the most current two release branches are `release-branch.go1.12` and `release-branch.go1.13`, from which new `Go 1.12.x` and `Go 1.13.x` releases are cut) Fixes for experimental ports are generally not backported.
+Our default decision should always be to not backport, but fixes for **security issues**, **serious problems with no workaround**, and **documentation fixes** are backported to the most recent two release branches, if applicable to that branch. (for example, the most current two release branches are `release-branch.go1.13` and `release-branch.go1.14`, from which new `Go 1.13.x` and `Go 1.14.x` releases are cut) Fixes for experimental ports are generally not backported.
 
 A “serious” problem is one that prevents a program from working at all. "Use a more recent stable version" is a valid workaround, so very few fixes will be backported to both previous issues.