From 0eb3e5736d2134b1ed2d14b3b25c831bd6adbec6 Mon Sep 17 00:00:00 2001
From: Robert Griesemer <gri@google.com>
Date: Thu, 9 Apr 2026 12:34:27 -0700
Subject: spec: fix prose in Instantiatons section

For #77273.

Change-Id: Idf5b81f77115e4e30921476f7424769fdf604ef4
Reviewed-on: https://go-review.googlesource.com/c/go/+/764920
Reviewed-by: Alan Donovan <adonovan@google.com>
TryBot-Bypass: Robert Griesemer <gri@google.com>
Auto-Submit: Robert Griesemer <gri@google.com>
Reviewed-by: Robert Griesemer <gri@google.com>
---
 doc/go_spec.html | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/go_spec.html b/doc/go_spec.html
index 88b2a68057..6cc64d7a19 100644
--- a/doc/go_spec.html
+++ b/doc/go_spec.html
@@ -1,6 +1,6 @@
 <!--{
 	"Title": "The Go Programming Language Specification",
-	"Subtitle": "Language version go1.27 (April 7, 2026)",
+	"Subtitle": "Language version go1.27 (April 9, 2026)",
 	"Path": "/ref/spec"
 }-->
 
@@ -4398,8 +4398,8 @@ of the corresponding type parameter. Otherwise instantiation fails.
 </ol>
 
 <p>
-Instantiating a type results in a new non-generic <a href="#Types">named type</a>;
-instantiating a function or method produces a new non-generic function or method.
+Instantiating a generic type, function, or method results in a non-generic type, function,
+or method, respectively.
 </p>
 
 <pre>
@@ -4412,7 +4412,7 @@ type parameter list    type arguments    after substitution
 </pre>
 
 <p>
-When using a generic function, type arguments may be provided explicitly,
+When using a generic function or method, type arguments may be provided explicitly,
 or they may be partially or completely <a href="#Type_inference">inferred</a>
 from the context in which the function is used.
 Provided that they can be inferred, type argument lists may be omitted entirely if the function is:
-- 
cgit v1.3