From: Ian Lance Taylor <iant@golang.org>
Date: Fri, 18 Aug 2023 16:44:16 +0000 (-0700)
Subject: spec: correct type parameter name used in example
X-Git-Tag: go1.22rc1~1215
X-Git-Url: http://www.git.cypherpunks.ru/?a=commitdiff_plain;h=ce16086345435d85906de31ea4af486b69bae895;p=gostls13.git

spec: correct type parameter name used in example

Change-Id: I40595a3f598483d029473af465c756f8777ecc91
Reviewed-on: https://go-review.googlesource.com/c/go/+/520915
Reviewed-by: Ian Lance Taylor <iant@google.com>
TryBot-Bypass: Ian Lance Taylor <iant@google.com>
Reviewed-by: Robert Griesemer <gri@google.com>
Auto-Submit: Ian Lance Taylor <iant@google.com>
---

diff --git a/doc/go_spec.html b/doc/go_spec.html
index 301fdb3cf1..a65e466fe4 100644
--- a/doc/go_spec.html
+++ b/doc/go_spec.html
@@ -1,6 +1,6 @@
 <!--{
 	"Title": "The Go Programming Language Specification",
-	"Subtitle": "Version of Aug 17, 2023",
+	"Subtitle": "Version of Aug 18, 2023",
 	"Path": "/ref/spec"
 }-->
 
@@ -4491,7 +4491,7 @@ the type parameters of the functions that need to be instantiated
 and for which no explicit type arguments is provided.
 These type parameters are called <i>bound</i> type parameters.
 For instance, in the <code>dedup</code> example above, the type parameters
-<code>P</code> and <code>E</code> are bound to <code>dedup</code>.
+<code>S</code> and <code>E</code> are bound to <code>dedup</code>.
 An argument to a generic function call may be a generic function itself.
 The type parameters of that function are included in the set of bound
 type parameters.