From: Kelby Faessler Date: Sat, 7 Jan 2023 15:31:03 +0000 (-0500) Subject: ✏ Fix typo in `docs/en/docs/deployment/concepts.md` (#5824) X-Git-Tag: 0.89.0~15 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=bea1fdd2eb34c9933bf66f08f9cc164ca97d99f1;p=thirdparty%2Ffastapi%2Ffastapi.git ✏ Fix typo in `docs/en/docs/deployment/concepts.md` (#5824) --- diff --git a/docs/en/docs/deployment/concepts.md b/docs/en/docs/deployment/concepts.md index 22604ceeb2..77419f8b0d 100644 --- a/docs/en/docs/deployment/concepts.md +++ b/docs/en/docs/deployment/concepts.md @@ -235,7 +235,7 @@ Here are some possible combinations and strategies: * One Uvicorn **process manager** would listen on the **IP** and **port**, and it would start **multiple Uvicorn worker processes** * **Kubernetes** and other distributed **container systems** * Something in the **Kubernetes** layer would listen on the **IP** and **port**. The replication would be by having **multiple containers**, each with **one Uvicorn process** running -* **Cloud services** that handle this for your +* **Cloud services** that handle this for you * The cloud service will probably **handle replication for you**. It would possibly let you define **a process to run**, or a **container image** to use, in any case, it would most probably be **a single Uvicorn process**, and the cloud service would be in charge of replicating it. !!! tip