Fixing bad links

Author: dannyroosevelt

docs-v2/pages/connect/index.mdx

@@ -11,7 +11,7 @@ You have full, code-level control over how these integrations work in your app.
 
 Connect lets you:
 
-1. Handle authorization or accept API keys on behalf of your users, for any of Pipedream's [{process.env.PUBLIC_APPS}+ APIs](https://pipedream.com/apps). Use the [Client SDK](https://github.com/PipedreamHQ/pipedream/tree/master/packages/sdk) or [Connect Link](/connect/quickstart#use-connect-link) to accept auth in minutes.
+1. Handle authorization or accept API keys on behalf of your users, for any of Pipedream's [{process.env.PUBLIC_APPS}+ APIs](https://pipedream.com/apps). Use the [Client SDK](https://github.com/PipedreamHQ/pipedream/tree/master/packages/sdk) or [Connect Link](/connect/quickstart#or-use-connect-link) to accept auth in minutes.
 2. Securely retrieve OAuth access tokens, API keys, and other credentials for your end users with Pipedream's [REST API](/connect/api)
 3. [Run workflows](/connect/workflows) for your end users with Pipedream's [workflow builder](/workflows), [serverless runtime](/), and thousands of no-code [triggers](/workflows/triggers) and [actions](/workflows/actions). Build complex integrations in minutes, writing code when you need it and using no-code components when you don't. Pipedream workflows are easy to modify, debug, and scale.
 4. [Embed any Pipedream action or trigger](/connect/components) to run on behalf of your users, directly from within your application.

docs-v2/pages/connect/oauth-clients.mdx

@@ -30,7 +30,7 @@ For any OAuth app that supports it, **you can always use your own client.** Your
 
 1. Follow the steps [here](/connected-accounts/oauth-clients#configuring-custom-oauth-clients) to create an OAuth client in Pipedream.
 2. When connecting an account either via the [frontend SDK](/connect/quickstart#use-the-pipedream-sdk-in-your-frontend), make sure to include the `oauthAppId` in `pd.connectAccount()`.
-3. If using [Connect Link](/connect/quickstart#use-connect-link), make sure to include the `oauthAppId` in the URL.
+3. If using [Connect Link](/connect/quickstart#or-use-connect-link), make sure to include the `oauthAppId` in the URL.
 
 ### Finding your OAuth app ID
 

docs-v2/pages/connect/quickstart.mdx

@@ -29,7 +29,7 @@ Here's how Connect sits in your frontend and backend, and communicates with Pipe
 You'll need to do two things to add Pipedream Connect to your app:
 
 1. [Connect to the Pipedream API from your server](#generate-a-short-lived-token). This lets you make secure calls to the Pipedream API to initiate the account connection flow and retrieve account credentials. If you're running a JavaScript framework like Node.js on your server, you can use the Pipedream SDK.
-2. [Add the Pipedream SDK to your frontend](#connect-a-users-account) or redirect your users to [a Pipedream-hosted URL](/connect/connect-link) to start the account connection flow.
+2. [Add the Pipedream SDK to your frontend](#connect-your-users-account) or redirect your users to [a Pipedream-hosted URL](/connect/connect-link) to start the account connection flow.
 
 We'll walk through these steps below, using [an example Next.js app](https://github.com/PipedreamHQ/pipedream-connect-examples/tree/master/managed-auth-basic-next-app/). To follow along, clone [the repo](https://github.com/PipedreamHQ/pipedream-connect-examples/) and follow the instructions in [the app's `README`](https://github.com/PipedreamHQ/pipedream-connect-examples/tree/master/managed-auth-basic-next-app/). That will run the app on `localhost:3000`.
 
@@ -74,7 +74,7 @@ You'll need these when configuring the SDK and making API requests.
 
 ### Generate a short-lived token
 
-To securely initiate account connections for your users, you'll need generate a short-lived token for your users and use that in the [account connection flow](#connect-a-users-account). See [the docs on Connect tokens](/connect/tokens) for a general overview of why we need to create tokens and scope them to end users.
+To securely initiate account connections for your users, you'll need generate a short-lived token for your users and use that in the [account connection flow](#connect-your-users-account). See [the docs on Connect tokens](/connect/tokens) for a general overview of why we need to create tokens and scope them to end users.
 
 In the Next.js example here, we're running [Next server components](https://nextjs.org/docs/app/building-your-application/rendering/server-components) in `app/server.ts`. We call the `serverConnectTokenCreate` method from the frontend to retrieve a token **for a specific user**.
 
@@ -88,7 +88,7 @@ const { token, expires_at } = await serverConnectTokenCreate({
 
 If you're using a different server / API framework, you'll need to make secure calls to that API to create a new token for your users.
 
-Once you have a token, return it to your frontend to start the account connection flow for the user, or redirect them to a Pipedream-hosted URL with [Connect Link](#use-connect-link).
+Once you have a token, return it to your frontend to start the account connection flow for the user, or redirect them to a Pipedream-hosted URL with [Connect Link](#or-use-connect-link).
 
 <Callout type="info">
 Refer to the API docs for [full set of parameters you can pass](/connect/api#create-a-new-token) in the `ConnectTokenCreate` call.
@@ -99,7 +99,7 @@ Refer to the API docs for [full set of parameters you can pass](/connect/api#cre
 To connect a third-party account for a user, you have two options:
 
 1. [Use the Pipedream SDK](#use-the-pipedream-sdk-in-your-frontend) in your frontend
-2. [Use Connect Link](#use-connect-link) to deliver a hosted URL to your user
+2. [Use Connect Link](#or-use-connect-link) to deliver a hosted URL to your user
 
 #### Use the Pipedream SDK in your frontend
 

docs-v2/pages/connect/troubleshooting.mdx

@@ -38,7 +38,7 @@ Connect tokens expire, and are only able to be used once. Try generating a new t
 
 _App not found. Please check your app id._
 
-Double-check the app slug you're passing [when connecting your user's account](/connect/quickstart#connect-a-users-account).
+Double-check the app slug you're passing [when connecting your user's account](/connect/quickstart#connect-your-users-account).
 
 ### Connection failed. Please retry or contact support.
 

docs-v2/pages/privacy-and-security/index.mdx

@@ -133,7 +133,7 @@ Tokens expire after 4 hours, at which point you must create a new token for that
 
 ### Connect Link
 
-You can also use [Connect Link](/connect/quickstart#use-connect-link) to generate a URL that initiates the authorization flow for a specific user. This is useful when you want to initiate the auth flow from a client-side environment that can't run JavaScript, or include the link in an email, chat message, etc.
+You can also use [Connect Link](/connect/connect-link) to generate a URL that initiates the authorization flow for a specific user. This is useful when you want to initiate the auth flow from a client-side environment that can't run JavaScript, or include the link in an email, chat message, etc.
 
 Like tokens, Connect Links are coupled to specific users, and expire after 4 hours.
 

docs-v2/vercel.json

@@ -281,6 +281,14 @@
     {
       "source": "/docs/connected-accounts/api",
       "destination": "/docs/connect/api#accounts"
+    },
+    {
+      "source": "/docs/connect/quickstart#use-connect-link",
+      "destination": "/docs/connect/quickstart#or-use-connect-link"
+    },
+    {
+      "source": "/docs/connect/quickstart#connect-a-users-account",
+      "destination": "/docs/connect/quickstart#connect-your-users-account"
     }
   ]
 }