From 67c8518ce305776939a13d37dd2eddf664da803e Mon Sep 17 00:00:00 2001
From: Motov Yurii <109919500+YuriiMotov@users.noreply.github.com>
Date: Tue, 11 Nov 2025 12:16:34 +0100
Subject: [PATCH] Apply suggestions from code review

---
 docs/en/docs/tutorial/query-params-str-validations.md | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/docs/en/docs/tutorial/query-params-str-validations.md b/docs/en/docs/tutorial/query-params-str-validations.md
index 6d04636016..07e6abbeaf 100644
--- a/docs/en/docs/tutorial/query-params-str-validations.md
+++ b/docs/en/docs/tutorial/query-params-str-validations.md
@@ -262,9 +262,13 @@ In other words, `None` is not an acceptable runtime value for query parameters 
 
 If you want to accept special values (like `"None"` or an empty string) and interpret them as `None` in your application, you can handle them manually in your function:
 
-{* ../../docs_src/query_params_str_validations/tutorial006d_an_py310.py hl[9,11] *}
+{* ../../docs_src/query_params_str_validations/tutorial006d_an_py310.py hl[9:13 18] *}
 
-> **Note**: This example uses `BeforeValidator`, which is only available in **Pydantic v2**.
+/// note
+
+This example uses `BeforeValidator`, which is only available in **Pydantic v2**.
+
+///
 
 ## Query parameter list / multiple values { #query-parameter-list-multiple-values }