Fix title capitalizations

Author: jverce

docs-v2/pages/connect/_meta.tsx

@@ -3,40 +3,40 @@ export default {
     "title": "Overview",
   },
   "use-cases": {
-    "title": "Use Cases",
+    "title": "Use cases",
   },
   "quickstart": {
     "title": "Quickstart",
   },
   "workflows": {
-    "title": "Running Workflows",
+    "title": "Running workflows",
   },
   "components": {
-    "title": "Running Components",
+    "title": "Running components",
   },
   "api": {
-    "title": "API & SDK Reference",
+    "title": "API & SDK reference",
   },
   "tokens": {
-    "title": "Connect Tokens",
+    "title": "Connect tokens",
   },
   "environments": {
     "title": "Environments",
   },
   "oauth-clients": {
-    "title": "OAuth Clients",
+    "title": "OAuth clients",
   },
   "webhooks": {
     "title": "Webhooks",
   },
   "connect-link": {
-    "title": "Connect Link",
+    "title": "Connect link",
   },
   "troubleshooting": {
     "title": "Troubleshooting",
   },
   "customize-your-app": {
-    "title": "Customize Your App",
+    "title": "Customize your app",
   },
   "migrating-from-project-keys-to-oauth": {
     "display": "hidden",

docs-v2/pages/connect/api.mdx

@@ -1,11 +1,11 @@
 import Callout from '@/components/Callout'
 import { Tabs } from 'nextra/components'
 
-# Connect API & SDK Reference
+# Connect API & SDK reference
 
 Pipedream provides a TypeScript SDK and a REST API to interact with the Connect service. You'll find examples using the SDK and the REST API in multiple languages below.
 
-## REST API Base URL
+## REST API base URL
 
 Pipedream Connect resources are scoped to [projects](/projects), so you'll need to pass [the project's ID](/projects#finding-your-projects-id) as a part of the base URL:
 
@@ -43,7 +43,7 @@ or a specific version:
 
 See the [REST API Authentication docs](/rest-api/auth).
 
-### TypeScript SDK (Server)
+### TypeScript SDK (server)
 
 Most of your interactions with the Connect API will happen on the server, to protect API requests and user credentials. You'll use the SDK in [your frontend](#typescript-sdk-browser) to let users connect accounts. Once connected, you'll use the SDK on the server to retrieve credentials, invoke workflows on their behalf, and more.
 
@@ -63,7 +63,7 @@ const pd = createBackendClient({
 // The `pd` client provides methods to interact with the Connect API — see below
 ```
 
-### TypeScript SDK (Browser)
+### TypeScript SDK (browser)
 
 You'll primarily use the browser SDK to let your users securely connect apps from your frontend. Here, you
 
@@ -667,7 +667,7 @@ curl -X GET \
 }
 ```
 
-##### Example Response (with `include_credentials=true`)
+##### Example response (with `include_credentials=true`)
 
 ```json
 {
@@ -954,7 +954,7 @@ Pipedream returns a `204 No Content` response on successful account deletion
 
 ### Components
 
-#### List Components
+#### List components
 
 List all the components in the Pipedream registry.
 
@@ -1060,8 +1060,8 @@ curl -X GET "https://api.pipedream.com/v1/connect/{your_project_id}/components?a
 </Tabs.Tab>
 </Tabs>
 
-##### Example Response
 
+##### Example response
 ```json
 {
   "page_info": {
@@ -1091,7 +1091,7 @@ curl -X GET "https://api.pipedream.com/v1/connect/{your_project_id}/components?a
 ```
 
 
-#### Retrieve a Component
+#### Retrieve a component
 
 Retrieve a specific component from the Pipedream registry.
 
@@ -1181,7 +1181,7 @@ curl -X GET "https://api.pipedream.com/v1/connect/{your_project_id}/components/g
 </Tabs.Tab>
 </Tabs>
 
-##### Example Response
+##### Example response
 
 ```json
 {
@@ -1219,7 +1219,7 @@ curl -X GET "https://api.pipedream.com/v1/connect/{your_project_id}/components/g
 
 
 
-#### Configure a Component
+#### Configure a component
 
 Configure the a component's prop, based on the current component's
 configuration. This endpoint will use the component's configuration to retrieve
@@ -1236,7 +1236,7 @@ GET /{component_type}/configure
 
 Either `triggers`, `actions`, or `components`.
 
-##### Body Parameters
+##### Body parameters
 
 `configured_props` **object**
 
@@ -1369,7 +1369,7 @@ curl -X GET "https://api.pipedream.com/v1/connect/{your_project_id}/components/c
 
 </Tabs>
 
-##### Example Response
+##### Example response
 
 ```json
 {
@@ -1418,7 +1418,7 @@ curl -X GET "https://api.pipedream.com/v1/connect/{your_project_id}/components/c
 }
 ```
 
-#### Reload a Component's Props (i.e. Configure Dynamic Props)
+#### Reload a component's props (i.e. configure dynamic props)
 
 Reload the component's props after configuring a dynamic prop, based on the
 current component's configuration. This endpoint will use the component's
@@ -1436,7 +1436,7 @@ GET /{component_type}/props
 
 Either `triggers`, `actions`, or `components`.
 
-##### Body Parameters
+##### Body parameters
 
 `configured_props` **object**
 
@@ -1580,7 +1580,7 @@ curl -X GET "https://api.pipedream.com/v1/connect/{your_project_id}/components/p
 
 </Tabs>
 
-##### Example Response
+##### Example response
 
 ```json
 {
@@ -1638,15 +1638,15 @@ curl -X GET "https://api.pipedream.com/v1/connect/{your_project_id}/components/p
 }
 ```
 
-#### Invoke an Action
+#### Invoke an action
 
 Invoke an action component for a Pipedream Connect user in a project.
 
 ```text
 POST /actions/run
 ```
 
-##### Body Parameters
+##### Body parameters
 
 `id` **string**
 
@@ -1787,7 +1787,7 @@ curl -X GET "https://api.pipedream.com/v1/connect/{your_project_id}/actions/run"
 
 </Tabs>
 
-##### Example Response
+##### Example response
 
 ```json
 {
@@ -1817,15 +1817,15 @@ curl -X GET "https://api.pipedream.com/v1/connect/{your_project_id}/actions/run"
 }
 ```
 
-#### Deploy a Trigger
+#### Deploy a trigger
 
 Deploy a trigger component for a Pipedream Connect user in a project.
 
 ```text
 POST /triggers/deploy
 ```
 
-##### Body Parameters
+##### Body parameters
 
 `id` **string**
 
@@ -1976,7 +1976,7 @@ curl -X GET "https://api.pipedream.com/v1/connect/{your_project_id}/triggers/dep
 
 </Tabs>
 
-##### Example Response
+##### Example response
 
 ```json
 {

docs-v2/pages/connect/components.mdx

@@ -3,13 +3,13 @@ import ArcadeEmbed from '@/components/ArcadeEmbed'
 import Callout from '@/components/Callout'
 import Image from 'next/image'
 
-# Running Components for Your End Users
+# Running components for your end users
 
 Pipedream Connect provides you with the ability to pre-configure, deploy and
 invoke [components](/components) **on behalf of [your end
 users](/connect/api#external-users)**.
 
-## What are Components?
+## What are components?
 
 In the context of Pipedream Connect, components are self-contained executable
 units of code. They are usually provided with some arbitrary input and produce a
@@ -20,9 +20,9 @@ repository](https://github.com/PipedreamHQ/pipedream/tree/master/components).
 To learn more about components in detail, please visit our [Components
 guide](/components).
 
-## How to Run Components for Your End Users
+## How to run components for your end users
 
-### Retrieving a Component's Definition
+### Retrieving a component's definition
 
 The first thing to do in order to run a component for your end users is to know
 about the component itself. To start with, you need to know the component's
@@ -214,7 +214,7 @@ the prop being configured as the value for the `prop_name` attribute.
 }
 ```
 
-#### Dynamic Props
+#### Dynamic props
 
 The set of props that a component can accept might not be static, and can change
 depending on the values of prior props. Props that behave this way are called
@@ -333,7 +333,7 @@ All this means is that actions can be invoked manually on demand, while sources
 are instead deployed and run automatically when the event they are listening for
 occurs.
 
-#### Invoking an Action
+#### Invoking an action
 
 At the end of the configuration process for an action, you'll end up with a
 payload that you can use to invoke the action. The payload is similar to the one
@@ -401,7 +401,7 @@ above:
 }
 ```
 
-#### Deploying a Source
+#### Deploying a source
 
 Because sources are exercised by events that happen on a third-party service,
 their semantics are different from actions. Once a source is configured, it must

docs-v2/pages/connect/use-cases.mdx

@@ -1,10 +1,10 @@
-# Pipedream Connect Use Cases
+# Pipedream Connect use cases
 
 Developers use Pipedream Connect to build customer-facing API integrations into their products. It lets you build [in-app messaging](#in-app-messaging), [CRM syncs](#crm-syncs), [AI-driven products](#ai-products), and much more, all in a few minutes.
 
 ## Core value to app developers
 
-In 20 years of building software, we've seen a common theme. No matter the product, your customers end up needing to connect your app to third-party APIs. 
+In 20 years of building software, we've seen a common theme. No matter the product, your customers end up needing to connect your app to third-party APIs.
 
 You might build real-time notifications with messaging apps, export customer data to databases or spreadsheets, ingest data from CRMs, or connect to any of the thousands of APIs and SaaS services your customers are using. These features are often tied to large contracts and Enterprise customers.
 
@@ -38,4 +38,4 @@ Sync data between your app and Google Sheets, Airtable, or any spreadsheet. Pipe
 
 ### And much more
 
-Building an app with Pipedream and want to be profiled here (anonymously or otherwise)? Email <code>[email protected]</code> to let us know!
+Building an app with Pipedream and want to be profiled here (anonymously or otherwise)? Email <code>[email protected]</code> to let us know!