design/43651-type-parameters: minor formatting/wording fixes
Change-Id: I94003ba5f108076abf85786374ee9d537353683c
Reviewed-on: https://go-review.googlesource.com/c/proposal/+/349069
Trust: Ian Lance Taylor <iant@golang.org>
Reviewed-by: Ian Lance Taylor <iant@golang.org>
diff --git a/design/43651-type-parameters.md b/design/43651-type-parameters.md
index 341124e..77e9b43 100644
--- a/design/43651-type-parameters.md
+++ b/design/43651-type-parameters.md
@@ -714,7 +714,7 @@
The same applies to embedded interface types.
For any two interface types `E1` and `E2`, the type set of `interface{
-E1; E2}` is the intersection of the type sets of `E1` and `E2`.
+E1; E2 }` is the intersection of the type sets of `E1` and `E2`.
Therefore, the type set of an interface type is the intersection of
the type sets of the element of the interface.
@@ -887,7 +887,7 @@
type set of the parameter's constraint.
This applies to operators like '<' or '+' or other general operators.
For special purpose operators like `range` loops, we permit their use
-of the type parameter has a structural constraint, as [defined
+if the type parameter has a structural constraint, as [defined
later](#Constraint-type-inference); the definition here is basically
that the constraint has a single underlying type.
If the function can be compiled successfully using each type in the
