From 3dcfbc7d87b3fc643478b93a5e4bc27a1f6fc3ce Mon Sep 17 00:00:00 2001
From: sangsaist <sanjaysangsai@gmail.com>
Date: Tue, 17 Mar 2026 19:05:37 +0530
Subject: [PATCH 1/2] Improve grammar and clarity in features documentation

---
 docs/en/docs/features.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/en/docs/features.md b/docs/en/docs/features.md
index eee11cd1ea..9eff7ca553 100644
--- a/docs/en/docs/features.md
+++ b/docs/en/docs/features.md
@@ -8,7 +8,7 @@
 
 * [**OpenAPI**](https://github.com/OAI/OpenAPI-Specification) for API creation, including declarations of <dfn title="also known as: endpoints, routes">path</dfn> <dfn title="also known as HTTP methods, as POST, GET, PUT, DELETE">operations</dfn>, parameters, request bodies, security, etc.
 * Automatic data model documentation with [**JSON Schema**](https://json-schema.org/) (as OpenAPI itself is based on JSON Schema).
-* Designed around these standards, after a meticulous study. Instead of an afterthought layer on top.
+* It is designed around these standards after a meticulous study, rather than being an afterthought layer on top.
 * This also allows using automatic **client code generation** in many languages.
 
 ### Automatic docs { #automatic-docs }
@@ -73,7 +73,7 @@ Pass the keys and values of the `second_user_data` dict directly as key-value ar
 
 ### Editor support { #editor-support }
 
-All the framework was designed to be easy and intuitive to use, all the decisions were tested on multiple editors even before starting development, to ensure the best development experience.
+The entire framework was designed to be easy and intuitive to use; all decisions were tested on multiple editors even before starting development to ensure the best experience.
 
 In the Python developer surveys, it's clear [that one of the most used features is "autocompletion"](https://www.jetbrains.com/research/python-developers-survey-2017/#tools-and-features).
 
@@ -147,7 +147,7 @@ FastAPI includes an extremely easy to use, but extremely powerful <dfn title='al
 
 ### Unlimited "plug-ins" { #unlimited-plug-ins }
 
-Or in other way, no need for them, import and use the code you need.
+In other words, there is no need for them; import and use the code you need.
 
 Any integration is designed to be so simple to use (with dependencies) that you can create a "plug-in" for your application in 2 lines of code using the same structure and syntax used for your *path operations*.
 
@@ -159,7 +159,7 @@ Any integration is designed to be so simple to use (with dependencies) that you
 
 ## Starlette features { #starlette-features }
 
-**FastAPI** is fully compatible with (and based on) [**Starlette**](https://www.starlette.dev/). So, any additional Starlette code you have, will also work.
+**FastAPI** is fully compatible with (and based on) [**Starlette**](https://www.starlette.dev/). So, any additional Starlette code you have will also work.
 
 `FastAPI` is actually a sub-class of `Starlette`. So, if you already know or use Starlette, most of the functionality will work the same way.
 

From 132055482a9f770f8a47b32efb1fc21a798d257e Mon Sep 17 00:00:00 2001
From: sangsaist <sanjaysangsai@gmail.com>
Date: Thu, 19 Mar 2026 22:40:31 +0530
Subject: [PATCH 2/2] fix: improve grammar and punctuation in query-params docs

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

diff --git a/docs/en/docs/tutorial/query-params.md b/docs/en/docs/tutorial/query-params.md
index efe2c6d7a0..20a490945b 100644
--- a/docs/en/docs/tutorial/query-params.md
+++ b/docs/en/docs/tutorial/query-params.md
@@ -21,7 +21,7 @@ As they are part of the URL, they are "naturally" strings.
 
 But when you declare them with Python types (in the example above, as `int`), they are converted to that type and validated against it.
 
-All the same process that applied for path parameters also applies for query parameters:
+All the same processes that apply to path parameters also apply to query parameters:
 
 * Editor support (obviously)
 * Data <dfn title="converting the string that comes from an HTTP request into Python data">"parsing"</dfn>
@@ -32,7 +32,7 @@ All the same process that applied for path parameters also applies for query par
 
 As query parameters are not a fixed part of a path, they can be optional and can have default values.
 
-In the example above they have default values of `skip=0` and `limit=10`.
+In the example above, they have default values of `skip=0` and `limit=10`.
 
 So, going to the URL:
 
@@ -107,7 +107,7 @@ or
 http://127.0.0.1:8000/items/foo?short=yes
 ```
 
-or any other case variation (uppercase, first letter in uppercase, etc), your function will see the parameter `short` with a `bool` value of `True`. Otherwise as `False`.
+or any other case variation (uppercase, first letter in uppercase, etc.), your function will see the parameter `short` with a `bool` value of `True`. Otherwise as `False`.
 
 
 ## Multiple path and query parameters { #multiple-path-and-query-parameters }
@@ -132,7 +132,7 @@ But when you want to make a query parameter required, you can just not declare a
 
 Here the query parameter `needy` is a required query parameter of type `str`.
 
-If you open in your browser a URL like:
+If you open a URL like this in your browser:
 
 ```
 http://127.0.0.1:8000/items/foo-item