From 2c2cda7236c78758c8b2b2f0a4cb46045bd8400f Mon Sep 17 00:00:00 2001
From: Serafim Dyachenko <75319000+pepellsd@users.noreply.github.com>
Date: Fri, 20 Sep 2024 20:36:23 +0300
Subject: [PATCH] Update exception.md (#1803)

delete dot)
---
 docs/docs/en/getting-started/middlewares/exception.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/docs/en/getting-started/middlewares/exception.md b/docs/docs/en/getting-started/middlewares/exception.md
index c9e7e3e69c..e50cbf3bdd 100644
--- a/docs/docs/en/getting-started/middlewares/exception.md
+++ b/docs/docs/en/getting-started/middlewares/exception.md
@@ -15,7 +15,7 @@ Sometimes, you need to register exception processors at the top level of your ap
 For this purpose, **FastStream** provides a special `ExceptionMiddleware`. You just need to create it, register handlers, and add it to the broker, router, or subscribers you want (as a [regular middleware](index.md){.internal-link}).
 
 ```python linenums="1"
-from faststream. import ExceptionMiddleware
+from faststream import ExceptionMiddleware
 
 exception_middleware = ExceptionMiddleware()