From 2a07d01c2ee4ace517183bf7e1de0404e5b08ee9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Rodrigo=20Gir=C3=A3o=20Serr=C3=A3o?=
 <5621605+rodrigogiraoserrao@users.noreply.github.com>
Date: Wed, 7 Dec 2022 17:07:14 +0000
Subject: [PATCH] Update responsive-app-background-task.md

---
 docs/blog/posts/responsive-app-background-task.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/blog/posts/responsive-app-background-task.md b/docs/blog/posts/responsive-app-background-task.md
index 47e496d37..d639541d6 100644
--- a/docs/blog/posts/responsive-app-background-task.md
+++ b/docs/blog/posts/responsive-app-background-task.md
@@ -69,7 +69,7 @@ It is by using the module `asyncio` from the standard library that our cook lear
 [Textual](https://github.com/textualize/textual) is an async framework, which means it knows how to interoperate with the module `asyncio` and this will be the solution to our problem.
 By using `asyncio` with the tasks we want to run in the background, we will let the application remain responsive while we load and parse the data we need, or while we crunch the numbers we need to crunch, or while we connect to some slow API over the Internet, or whatever it is you want to do.
 
-The module `asyncio` introduces a keyword `async` that you can use to identify functions that you want to be able to run asynchronously.
+The module `asyncio` uses the keyword `async` to know which functions can be run asynchronously.
 In other words, you use the keyword `async` to identify functions that contain tasks that would otherwise force the cook to waste time.
 (Functions with the keyword `async` are called _coroutines_.)