Update API reference links to match capitalized section headers

Author: dannyroosevelt

docs-v2/pages/connect/components.mdx

@@ -821,7 +821,7 @@ These are 2 categories of triggers you can deploy on behalf of your end users:
 - [Native triggers](#native-triggers)
 
 <Callout type="info">
-Refer to the [full Connect API reference](/connect/api/#deploy-a-trigger) to list, retrieve, delete, and manage triggers for your user.
+Refer to the [full Connect API reference](/connect/api/#deploy-trigger) to list, retrieve, delete, and manage triggers for your user.
 </Callout>
 
 ### App-based event sources

docs-v2/pages/connect/workflows.mdx

@@ -358,13 +358,13 @@ curl -X POST https://{your-endpoint-url} \
 
 ### Deploy an event source
 
-You can [programmatically deploy triggers via the API](/connect/api/#deploy-a-trigger) to have events from integrated apps (like [new Slack messages](https://pipedream.com/apps/slack/triggers/new-message-in-channels) or [new emails in Gmail](https://pipedream.com/apps/gmail/triggers/new-email-received)) trigger your workflow. This allows you to:
+You can [programmatically deploy triggers via the API](/connect/api/#deploy-trigger) to have events from integrated apps (like [new Slack messages](https://pipedream.com/apps/slack/triggers/new-message-in-channels) or [new emails in Gmail](https://pipedream.com/apps/gmail/triggers/new-email-received)) trigger your workflow. This allows you to:
 
 - Deploy triggers for specific users from your application
 - Configure trigger parameters per-user
 - Manage deployed triggers via the API
 
-See the [API documentation](/connect/api/#deploy-a-trigger) for detailed examples of deploying and managing triggers.
+See the [API documentation](/connect/api/#deploy-trigger) for detailed examples of deploying and managing triggers.
 
 ## OAuth client requirements