design/go2draft-type-parameters: fix typo
Change-Id: I5a9e9f3098de0a926637e2b4b8bc17272fe1cfbc
GitHub-Last-Rev: a17d5ed1de0cc9397399e4329a2aac5f976d78c7
GitHub-Pull-Request: golang/proposal#32
Reviewed-on: https://go-review.googlesource.com/c/proposal/+/284212
Reviewed-by: Bryan C. Mills <bcmills@google.com>
diff --git a/design/go2draft-type-parameters.md b/design/go2draft-type-parameters.md
index c75eb75..2325c32 100644
--- a/design/go2draft-type-parameters.md
+++ b/design/go2draft-type-parameters.md
@@ -765,7 +765,7 @@
compare values of that type and can call the `Hash` method.
It's possible to use `comparable` to produce a constraint that can not
-be satisifed by any type.
+be satisfied by any type.
```
// ImpossibleConstraint is a type constraint that no type can satisfy,
@@ -946,7 +946,7 @@
write out some or all of the type arguments.
We can use _function argument type inference_ for a function call to
deduce type arguments from the types of the non-type arguments.
-We can use _contraint type inference_ to deduce unknown type arguments
+We can use _constraint type inference_ to deduce unknown type arguments
from known type arguments.
In the examples above, when instantiating a generic function or type,
@@ -2592,7 +2592,7 @@
Constraint type inference lets us give a name to the element of a
slice type, and to apply other similar type decompositions.
However, there is no way to associate a float type and a complex type.
-For example, there is no way to write the predecared `real`, `imag`,
+For example, there is no way to write the predeclared `real`, `imag`,
or `complex` functions with this design draft.
There is no way to say "if the argument type is `complex64`, then the
result type is `float32`."
