From 96dc79e84dd5fd999fc4bf9a78c9e8ec3e469cfe Mon Sep 17 00:00:00 2001
From: alv2017 <v.alishauskaite@gmail.com>
Date: Sat, 22 Mar 2025 13:25:46 +0200
Subject: [PATCH] docs/tutorial/middleware.md: new section added: HTTP
 Middleware

---
 docs/en/docs/tutorial/middleware.md | 15 +++++++++++++--
 1 file changed, 13 insertions(+), 2 deletions(-)

diff --git a/docs/en/docs/tutorial/middleware.md b/docs/en/docs/tutorial/middleware.md
index 64125dc74..2124954d9 100644
--- a/docs/en/docs/tutorial/middleware.md
+++ b/docs/en/docs/tutorial/middleware.md
@@ -65,11 +65,22 @@ Here we use <a href="https://docs.python.org/3/library/time.html#time.perf_count
 
 ///
 
-### Class-Based Middleware
+## HTTP Middleware
+
+As you noticed the decorator `@app.middleware('http')` contains a parameter called `http`. 
+
+This parameter defines the type of server events to be handled by the middleware. 
+
+ASGI server supports the following scope types (or event types): `lifespan`, `http`, and `websocket`.
+
+The `http` middleware is designed to work with HTTP protocol, and it is responsible for handling of HTTP requests and responses.
+
+
+## Class-Based Middleware
 
 It is possible to define a custom `http` middleware using classes.
 
-We will implement the class-based middleware with exactly the same functionality as in the example above.
+We will implement a class-based middleware with exactly the same functionality as in the example with the `@app.middleware('http')` decorator.
 
 We will use an abstract `BaseHTTPMiddleware` class from Starlette that allows to write custom `http` middlewares.