Merge branch 'develop' into feature/scheduled-task

Author: s3rius

docs/extending-taskiq/README.md

@@ -14,6 +14,6 @@ All abstract classes can be found in `taskiq.abc` package.
 
 - [Brokers](./broker.md)
 - [Middlewares](./middleware.md)
-- [Result backends](./resutl-backend.md)
+- [Result backends](./result-backend.md)
 - [CLI](./cli.md)
 - [Schedule sources](./schedule-sources.md)

docs/extending-taskiq/middleware.md

@@ -6,7 +6,7 @@ order: 2
 
 Middlewares are super helpful. You can inject some code before or after task's execution.
 
-Middlewares must implement `taskiq.abc.middleware.TaskiqMiddleware` abstract class.
+Middlewares must implement [`taskiq.abc.middleware.TaskiqMiddleware`](https://github.com/taskiq-python/taskiq/blob/master/taskiq/abc/middleware.py) abstract class.
 Every method of a middleware can be either sync or async. Taskiq will execute it
 as you expect.
 

docs/extending-taskiq/resutl-backend.md renamed to docs/extending-taskiq/result-backend.md

@@ -135,7 +135,7 @@ def _signal_handler(signum: int, _frame: Any) -> None:
 
         logger.debug(f"Got signal {signum}.")
         action_queue.put(ShutdownAction())
-        logger.warn("Workers are scheduled for shutdown.")
+        logger.warning("Workers are scheduled for shutdown.")
 
     return _signal_handler