From 567774be636e50261874403e446b906552796613 Mon Sep 17 00:00:00 2001
From: "pre-commit-ci-lite[bot]"
 <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>
Date: Fri, 9 Jan 2026 11:00:58 +0000
Subject: [PATCH] =?UTF-8?q?=F0=9F=8E=A8=20Auto=20format?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/en/docs/advanced/response-change-status-code.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/docs/en/docs/advanced/response-change-status-code.md b/docs/en/docs/advanced/response-change-status-code.md
index 4a258d8f5..be57b41ee 100644
--- a/docs/en/docs/advanced/response-change-status-code.md
+++ b/docs/en/docs/advanced/response-change-status-code.md
@@ -30,7 +30,7 @@ And if you declared a `response_model`, it will still be used to filter and conv
 
 You can also declare the `Response` parameter in dependencies, and set the status code in them. But keep in mind that the last one to be set will win.
 
-## Notes
+## Notes { #notes }
 
 The `status_code` can be set dynamically depending on your application logic.
 
@@ -41,4 +41,3 @@ For example, you might return:
 - `204 No Content` when no response body is needed
 
 This allows reusing the same path operation while still returning accurate HTTP status codes.
-