From f0ee521a5c99065fc84ddb3cd7ed84af9706d12f Mon Sep 17 00:00:00 2001
From: "Lan, Jian" <45252210+ShapelessCat@users.noreply.github.com>
Date: Sat, 12 Jun 2021 01:22:07 -0700
Subject: [PATCH] Fix why-scala-3.md

The second `LinearSeq` of the clause "traits like `LinearSeq` and `LinearSeq`" should be another trait.
---
 _overviews/scala3-book/why-scala-3.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_overviews/scala3-book/why-scala-3.md b/_overviews/scala3-book/why-scala-3.md
index 1c23d1e7f0..e5f317f9f3 100644
--- a/_overviews/scala3-book/why-scala-3.md
+++ b/_overviews/scala3-book/why-scala-3.md
@@ -45,7 +45,7 @@ For instance, a `List` is defined as a class---technically it’s an abstract cl
 val x = List(1, 2, 3)
 ```
 
-However, what appears to the programmer to be a simple `List` is actually built from a combination of several specialized types, including an abstract class named `AbstractSeq`, traits like `LinearSeq` and `LinearSeq`, and more.
+However, what appears to the programmer to be a simple `List` is actually built from a combination of several specialized types, including an abstract class named `AbstractSeq`, traits like `LinearSeq` and `LinearSeqOps`, and more.
 Those types are similarly composed of other small, modular units of code.
 
 In addition to building a type like `List` from a series of modular traits, the `List` API also consists of dozens of other methods, many of which are higher-order functions: