Merge pull request #2392 from amohrland/am/doc-fix

typelevel · Oct 7, 2021 · e4f0f66 · e4f0f66
2 parents 1aeb53b + 5c96366
commit e4f0f66
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/std/dispatcher.md b/docs/std/dispatcher.md
@@ -8,7 +8,7 @@ title: Dispatcher
 ## Motivation
 
 Users of cats effect 2 may be familiar with the `Effect` and `ConcurrentEffect`
-typeclasses. These have been removed as they contrained implementations of the
+typeclasses. These have been removed as they constrained implementations of the
 typeclasses too much by forcing them to be embeddable in `IO` via `def
 toIO[A](fa: F[A]): IO[A]`. However, these typeclasses also had a valid use-case
 for unsafe running of effects to interface with impure APIs (`Future`, `NIO`,

diff --git a/docs/std/supervisor.md b/docs/std/supervisor.md
@@ -9,7 +9,7 @@ There are multiple ways to spawn a fiber to run an action:
 
 `Spawn[F]#start`: start and forget, no lifecycle management for the spawned fiber 
 
-`Concurrent[F]#background`: ties the lifecycle of the spawned fiber to that of the fiber that invoked `background`
+`Spawn[F]#background`: ties the lifecycle of the spawned fiber to that of the fiber that invoked `background`
 
 But what if we want to spawn a fiber that should outlive the scope that created
 it, but we still want to control its lifecycle?