From dab39c719b6e3a071283ba7301769ecfa8ff46d3 Mon Sep 17 00:00:00 2001 From: Will McGugan Date: Wed, 15 Mar 2023 15:51:30 +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 a33b807b7..11682c4ef 100644 --- a/docs/blog/posts/await-me-maybe.md +++ b/docs/blog/posts/await-me-maybe.md @@ -69,7 +69,7 @@ if __name__ == "__main__": ## Optionally awaitable -The "await me maybe" pattern is great when an async framework calls the app's code. The app developer can chose to write async code or not. Things get a little more complicated when the an app wants to call the framework's API. If the API has *asynced all the things*, then it would force the app to do the same. +The "await me maybe" pattern is great when an async framework calls the app's code. The app developer can choose to write async code or not. Things get a little more complicated when the app wants to call the framework's API. If the API has *asynced all the things*, then it would force the app to do the same. 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).