aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/HigherKinded-v2.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/HigherKinded-v2.md b/docs/HigherKinded-v2.md
index e30f4e429..3216f42f4 100644
--- a/docs/HigherKinded-v2.md
+++ b/docs/HigherKinded-v2.md
@@ -75,7 +75,7 @@ Type parameters in the encodings
The notion of type parameters makes sense even for encoded types,
which do not contain parameter lists in their syntax. Specifically,
the type parameters of a type are a sequence of type fields that
-correspond to paraneters in the unencoded type. They are determined as
+correspond to parameters in the unencoded type. They are determined as
follows.
- The type parameters of a class or trait type are those parameter fields declared in the class
@@ -176,7 +176,7 @@ have more than one type parameter. For instance, here is a trait with contravari
trait Lambda$NP[type -$hkArg$0, +$hkArg1] { type +Apply } extends Lambda$IP with Lambda$NI
Aside: the `+` prefix in front of `Apply` indicates that `Apply` is a covariant type field. Dotty
-admits variance annotations on type members).
+admits variance annotations on type members.
The definition of `Lambda$NP` shows that `Lambda` traits form a subtyping hierarchy: Traits which
have covariant or contravariant type parameters are subtypes of traits which don't. The supertraits