From d4a7ad713c670e60f3ba5265f31f0a359f86f24e Mon Sep 17 00:00:00 2001
From: omahs <73983677+omahs@users.noreply.github.com>
Date: Sun, 3 Sep 2023 15:10:19 +0200
Subject: [PATCH] fix typos

---
 docs/documentation/guides/python.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/documentation/guides/python.mdx b/docs/documentation/guides/python.mdx
index 2c558a69c..50ee44a86 100644
--- a/docs/documentation/guides/python.mdx
+++ b/docs/documentation/guides/python.mdx
@@ -27,7 +27,7 @@ Now that we've created a project and added a secret to its development environme
 
 ## Create a Python app
 
-For this demonstration, we use a minimal Flask application. However, the same principles will apply for any Python application such as those built with Django.
+For this demonstration, we use a minimal Flask application. However, the same principles will apply to any Python application such as those built with Django.
 
 ### Create a Flask app
 
@@ -103,7 +103,7 @@ At this stage, you know how to fetch secrets from Infisical back to your Python
         Although the SDK requires you to pass in a token, it enables greater efficiency and security
         than if you managed dozens of secrets yourself without it. Here're some benefits:
 
-        - You always pull in the right secrets because they're fetched on demand from a centralize source that is Infisical.
+        - You always pull in the right secrets because they're fetched on demand from a centralized source that is Infisical.
         - You can use the Infisical which comes with tons of benefits like secret versioning, access controls, audit logs, etc.
         - You now risk leaking one token that can be revoked instead of dozens of raw secrets.