diff --git a/en/plugins/quick-start/develop-plugins/tool-oauth.mdx b/en/plugins/quick-start/develop-plugins/tool-oauth.mdx
index caa49772..78071521 100644
--- a/en/plugins/quick-start/develop-plugins/tool-oauth.mdx
+++ b/en/plugins/quick-start/develop-plugins/tool-oauth.mdx
@@ -17,10 +17,12 @@ OAuth in Dify involves **two separate flows** that developers should understand
 <Note>
   On Dify Cloud, Dify team would create OAuth apps for popular tool plugins and set up OAuth clients, saving users the trouble to configure this themselves.
 
-  Admins of Self-Hosted Dify instances must go through this set up flow.
+  Admins of Self-Hosted Dify instances must go through this setup flow.
 </Note>
 
-Dify instance's admin / developer first need to register an OAuth app at the third-party service as a trusted application. From this, they'll be able to obtain the necessary credentials to configure the Dify tool provider as an OAuth client. As an example, here are the steps to setting up an OAuth client for Dify's Gmail tool provider:
+Dify instance's admins or developers first need to register an OAuth app at the third-party service as a trusted application. From this, they'll be able to obtain the necessary credentials to configure the Dify tool provider as an OAuth client. 
+
+As an example, here are the steps to setting up an OAuth client for Dify's Gmail tool provider:
 
 <AccordionGroup>
   <Accordion title="Create a Google Cloud Project">
@@ -94,7 +96,7 @@ After configuring OAuth clients, individual Dify users can now authorize your pl
 
 ### 1. Define OAuth schema in provider manifest
 
-The `oauth_schema` section of the provider manifest definitions tell Dify what credentials your plugin OAuth needs and what the OAuth flow will produce. Two schemas are required for setting up OAuth:
+The `oauth_schema` section of the provider manifest definitions tells Dify what credentials your plugin OAuth needs and what the OAuth flow will produce. Two schemas are required for setting up OAuth:
 
 #### client_schema