From 3b091c4e1082cb99d56046e9e8e541af3d332798 Mon Sep 17 00:00:00 2001 From: Karol Lewandowski Date: Tue, 18 Feb 2025 17:28:56 +0100 Subject: [PATCH] execution_contexts.md: Format content --- .../architectural_overview/threading/execution_contexts.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/topics/basics/architectural_overview/threading/execution_contexts.md b/topics/basics/architectural_overview/threading/execution_contexts.md index 002ebb8d0..52f0430a7 100644 --- a/topics/basics/architectural_overview/threading/execution_contexts.md +++ b/topics/basics/architectural_overview/threading/execution_contexts.md @@ -109,8 +109,8 @@ The following table presents the possibilities and APIs to use for reporting pro
  • RawProgressReporter - a raw text, details, and fraction reporting (invoked via reportRawProgress())
  • - Any report*Progress() function must be used inside withBackgroundProgress(), withModalProgress(), or runWithModalProgressBlocking() from tasks.kt. - Otherwise, if there is no reporter in the context, using `report*Progress()` will have no effect. + Any report*Progress() function must be used inside withBackgroundProgress(), withModalProgress(), or runWithModalProgressBlocking() from tasks.kt. + Otherwise, if there is no reporter in the context, using report*Progress() will have no effect. Example: