refine quick start docs

i18n/en/docusaurus-plugin-content-docs/current/quick/快速开始/请求数据结构.md

@@ -81,7 +81,7 @@ Let's try an invalid parameter request at http://127.0.0.1:8000/, and we can see
 In this chapter, we learned to avoid the problem of hardcoding parameter names by using structured request objects, allowing for better maintenance of parameter names, descriptions, and type definitions.
 
 However, there are still areas for improvement in this sample code:
-- The `r.Parse` non-business operation and should be handled separately from business logic.
+- The `r.Parse` is non-business operation and should be handled separately from business logic.
 - If there are many APIs, performing `r.Parse` in all of them becomes cumbersome.
 - Regarding data validation, if there are many API parameters, performing numerous `if` data validation operations becomes overly cumbersome.