diff --git a/docs-v2/pages/connect/api-proxy.mdx b/docs-v2/pages/connect/api-proxy.mdx
index 93d49090df2a9..00348cc835286 100644
--- a/docs-v2/pages/connect/api-proxy.mdx
+++ b/docs-v2/pages/connect/api-proxy.mdx
@@ -44,7 +44,7 @@ Since Pipedream has {process.env.PUBLIC_APPS}+ integrated apps, we know how the
 **URL**
 
 - The URL of the API you want to call (ex, `https://slack.com/api/chat.postMessage`)
-- When using the REST API, this should be an URL-safe Base64 encoded string (ex, `aHR0cHM6Ly9zbGFjay5jb20vYXBpL2NoYXQucG9zdE1lc3NhZ2U`)
+- When using the REST API, this should be a URL-safe Base64 encoded string (ex, `aHR0cHM6Ly9zbGFjay5jb20vYXBpL2NoYXQucG9zdE1lc3NhZ2U`)
 
 <Callout type="info">
 - Some APIs like Zendesk, Zoho, and others use dynamic base domains that are account-specific (e.g, `https://foo.zendesk.com`). For any of these apps, you should pass a relative path as the `url` in your proxy request, like `/api/v2/chat/chats` for example.
@@ -140,4 +140,4 @@ curl -X POST "https://api.pipedream.com/v1/connect/{your_project_id}/proxy/{url_
 The Connect proxy limits API requests to,
 - 100 requests per minute per project. Requests that surpass this limit will receive a `429` response.
 - A maximum timeout of 30 seconds. Requests that take longer than 30 seconds will be terminated, and Pipedream will return a `504` error to the caller.
-- [Let us know](https://pipedream.com/support) if you need higher limits.
+- Please [let us know](https://pipedream.com/support) if you need higher limits.