From dfa115290bb8b10077870149485673b59ff5c3d9 Mon Sep 17 00:00:00 2001 From: Andrey Sobolev Date: Tue, 22 Apr 2025 17:13:47 +0300 Subject: [PATCH] Fix link to Celery docs --- content/manuals/build/building/best-practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/manuals/build/building/best-practices.md b/content/manuals/build/building/best-practices.md index 68ea0de2672b..eb308bcf862a 100644 --- a/content/manuals/build/building/best-practices.md +++ b/content/manuals/build/building/best-practices.md @@ -147,7 +147,7 @@ Limiting each container to one process is a good rule of thumb, but it's not a hard and fast rule. For example, not only can containers be [spawned with an init process](/manuals/engine/containers/multi-service_container.md), some programs might spawn additional processes of their own accord. For -instance, [Celery](https://docs.celeryproject.org/) can spawn multiple worker +instance, [Celery](https://docs.celeryq.dev/) can spawn multiple worker processes, and [Apache](https://httpd.apache.org/) can create one process per request.