From d441bad09d40bc711993561df5a5ca1d58eec275 Mon Sep 17 00:00:00 2001
From: Kamil Rybacki <76902941+kamilrybacki@users.noreply.github.com>
Date: Mon, 15 Jul 2024 14:32:45 +0200
Subject: [PATCH] Update reflections.mdx

---
 src/content/articles/reflections.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/content/articles/reflections.mdx b/src/content/articles/reflections.mdx
index cc479633..db92b0d2 100644
--- a/src/content/articles/reflections.mdx
+++ b/src/content/articles/reflections.mdx
@@ -57,14 +57,14 @@ the input data. It also allows You to serialize and deserialize those models to
 However, these JSON schemas do not contain information about one of the most flexible aspects of data validation - the **custom validators**,
 which can be defined **programmatically** in the Python code. So that is one of the issues that I want to tackle.
 
-Also, while on the topic of allowing custom validators, I want their definitions to be as **flexible** as possible,
+Being on the topic of allowing custom validators, I want their definitions to be as **flexible** as possible,
 while remembering that somebody can use a cheeky `eval` to inject some malicious code into the system or
 `shutil.rmtree` to delete the whole filesystem.
 
 Also, when You dump a Pydantic model to JSON, the schema is often not very human-readable and it is not easy to
 maintain it in a repository. I want to structure my schema definitions in such a way, that a maintainer can easily
 see which fields are required, which are optional, which have default values, which are of a specific type and which
-are basically nested schemas themselves. Also, YAML has a couple of nice tricks up its sleeve such as **anchors** and
+are basically nested schemas themselves. Additionally, YAML has a couple of nice tricks up its sleeve such as **anchors** and
 **references** that can be used to define a schema in a more [DRY way].
 
 ### How it do? 🤔