From 01045e6b7feae641db6e38de08371302be8027f5 Mon Sep 17 00:00:00 2001 From: Will McGugan Date: Wed, 15 Mar 2023 16:00:55 +0000 Subject: [PATCH] Update docs/blog/posts/await-me-maybe.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Rodrigo Girão Serrão <5621605+rodrigogiraoserrao@users.noreply.github.com> --- docs/blog/posts/await-me-maybe.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/blog/posts/await-me-maybe.md b/docs/blog/posts/await-me-maybe.md index 11682c4ef..d44dd60db 100644 --- a/docs/blog/posts/await-me-maybe.md +++ b/docs/blog/posts/await-me-maybe.md @@ -73,7 +73,7 @@ The "await me maybe" pattern is great when an async framework calls the app's co Textual's API consists of regular methods for the most part, but there are a few methods which are optionally awaitable. These are *not* coroutines (which must be awaited to do anything). -In practice, this means that those API calls initiate something which will complete a short time later. If you discard the return value then it won't prevent it from working. You only need to `await` if you want to to know when it has finished. +In practice, this means that those API calls initiate something which will complete a short time later. If you discard the return value then it won't prevent it from working. You only need to `await` if you want to know when it has finished. The `mount` method is one such method. Calling it will add a widget to the screen: