From df5fc93faec22b28a4ef06fc31f4c5988e70bbc4 Mon Sep 17 00:00:00 2001 From: Hanbit Kang <58168528+hanbikan@users.noreply.github.com> Date: Thu, 18 May 2023 20:26:00 +0900 Subject: [PATCH] Remove unnecessary newline (#3756) --- docs/topics/shared-mutable-state-and-concurrency.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/topics/shared-mutable-state-and-concurrency.md b/docs/topics/shared-mutable-state-and-concurrency.md index 8e491b3d64..bcce95273a 100644 --- a/docs/topics/shared-mutable-state-and-concurrency.md +++ b/docs/topics/shared-mutable-state-and-concurrency.md @@ -195,8 +195,7 @@ state or to complex operations that do not have ready-to-use thread-safe impleme _Thread confinement_ is an approach to the problem of shared mutable state where all access to the particular shared state is confined to a single thread. It is typically used in UI applications, where all UI state is confined to -the single event-dispatch/application thread. It is easy to apply with coroutines by using a -single-threaded context. +the single event-dispatch/application thread. It is easy to apply with coroutines by using a single-threaded context.