From 5ecd7783315232d24c601e8a83b9a3111d63713e Mon Sep 17 00:00:00 2001
From: "pre-commit-ci[bot]"
 <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Date: Mon, 26 Feb 2024 13:14:53 +0000
Subject: [PATCH] =?UTF-8?q?=F0=9F=8E=A8=20[pre-commit.ci]=20Auto=20format?=
 =?UTF-8?q?=20from=20pre-commit.com=20hooks?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/en/docs/how-to/separate-openapi-schemas.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/en/docs/how-to/separate-openapi-schemas.md b/docs/en/docs/how-to/separate-openapi-schemas.md
index 161e39d3a..b708024d3 100644
--- a/docs/en/docs/how-to/separate-openapi-schemas.md
+++ b/docs/en/docs/how-to/separate-openapi-schemas.md
@@ -7,7 +7,7 @@ In fact, in some cases, it will even have **two JSON Schemas** in OpenAPI for th
 Let's see how that works and how to change it if you need to do that.
 
 !!! info
-    In the current behavior of pydantic separate output schemas are only created if the config 
+    In the current behavior of pydantic separate output schemas are only created if the config
     option `json_schema_serialization_defaults_required` is set to `True`.
 
 ## Pydantic Models for Input and Output