fix link typos

Author: andrewjschuang

docs-v2/pages/connect/api.mdx

@@ -403,7 +403,7 @@ GET /{project_id}/accounts/
 
 The ID or name slug the app you'd like to retrieve. For example, Slack's unique app ID is `app_OkrhR1`, and its name slug is `slack`.
 
-You can find the app's ID in the response from the [List apps]((/core/rest-api/#list-apps) endpoint, and the name slug under the **Authentication** section of any [app page](https://pipedream.com/apps).
+You can find the app's ID in the response from the [List apps](/core/rest-api/#list-apps) endpoint, and the name slug under the **Authentication** section of any [app page](https://pipedream.com/apps).
 
 ---
 
@@ -1113,7 +1113,7 @@ The ID or name slug the app you'd like to retrieve. For example, Slack's unique
 app ID is `app_OkrhR1`, and its name slug is `slack`.
 
 You can find the app's ID in the response from the [List
-apps]((/core/rest-api/#list-apps) endpoint, and the name slug under the
+apps](/core/rest-api/#list-apps) endpoint, and the name slug under the
 **Authentication** section of any [app page](https://pipedream.com/apps).
 
 ---

docs-v2/pages/connect/components.mdx

@@ -33,7 +33,7 @@ Check out the [public demo app](https://pdrm.co/connect) to see the API and SDK
 <Callout type="info">
 Refer to the [Connect API docs](/connect/api/) for the full API reference. Below is a quickstart with a few specific examples.
 
-You can skip steps 1 and 2 if you already know the component you want to use or if you'd prefer to [pass a natural language prompt to Pipedream's component search API]((/core/rest-api/#search-for-registry-components).
+You can skip steps 1 and 2 if you already know the component you want to use or if you'd prefer to [pass a natural language prompt to Pipedream's component search API](/core/rest-api/#search-for-registry-components).
 </Callout>
 
 <Steps>
@@ -676,9 +676,9 @@ above:
 
 #### 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 
-be deployed to start listening for events. When deploying a source, you 
+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
+be deployed to start listening for events. When deploying a source, you
 can define either a webhook URL or a Pipedream workflow ID to consume those events.
 
 Deploying a source is done by sending a payload similar to the one used for

docs-v2/pages/connect/managed-auth/quickstart.mdx

@@ -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-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.
+To securely initiate account connections for your users, you'll need to 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**.
 

docs-v2/pages/connect/workflows.mdx

@@ -263,11 +263,11 @@ You have two options for triggering workflows that run on behalf of your end use
 
 ### HTTP Webhook
 
-The most common way to trigger workflows is via HTTP webhook. We strongly recommend [creating a Pipedream OAuth client]((/core/rest-api/auth#creating-an-oauth-client) and authenticating inbound requests to your workflows.
+The most common way to trigger workflows is via HTTP webhook. We strongly recommend [creating a Pipedream OAuth client](/core/rest-api/auth#creating-an-oauth-client) and authenticating inbound requests to your workflows.
 
 To get started, you'll need:
 
-- [OAuth client ID and secret]((/core/rest-api/auth#creating-an-oauth-client) (optional but recommended)
+- [OAuth client ID and secret](/core/rest-api/auth#creating-an-oauth-client) (optional but recommended)
 - Your [project ID](/core/projects/#finding-your-projects-id)
 - Your workflow's HTTP endpoint URL
 - The [external user ID](/connect/api/#external-users) of your end user

docs-v2/pages/core/cli/reference.mdx

@@ -121,7 +121,7 @@ Generate new app and component files from templates.
 
 #### `pd init app`
 
-Creates a directory and [an app file](/(/core/core/contributing/components/guidelines/#app-files) from a template
+Creates a directory and [an app file](/core/core/contributing/components/guidelines/#app-files) from a template
 
 ```bash
 # Creates google_calendar/ directory and google_calendar.mjs file
@@ -146,7 +146,7 @@ Creates a new directory and [an event source](/core/workflows/triggers/) from a
 pd init source cancelled-event
 ```
 
-You can attach [database](/core/contributing/components/api//#db), [HTTP](/core/contributing/components/api//#http), or [Timer](/core/contributing/components/api//#timer) props to your template using the following flags:
+You can attach [database](/core/contributing/components/api/#db), [HTTP](/core/contributing/components/api/#http), or [Timer](/core/contributing/components/api/#timer) props to your template using the following flags:
 
 | Prop type | Flag      |
 | --------- | --------- |

docs-v2/pages/core/contributing/components/actions-quickstart.mdx

@@ -57,7 +57,7 @@ We recommend that you complete the examples below in order.
 
 ### hello world!
 
-The following code represents a simple component that can be published as an action ([learn more](/core/contributing/components/api//) about the component structure). When used in a workflow, it will export `hello world!` as the return value for the step.
+The following code represents a simple component that can be published as an action ([learn more](/core/contributing/components/api/) about the component structure). When used in a workflow, it will export `hello world!` as the return value for the step.
 
 ```javascript
 export default {
@@ -109,7 +109,7 @@ Keep the browser tab open. We'll return to this workflow in the rest of the exam
 
 ### hello [name]!
 
-Next, let's update the component to capture some user input. First, add a `string` [prop](/core/contributing/components/api//#props) called `name` to the component.
+Next, let's update the component to capture some user input. First, add a `string` [prop](/core/contributing/components/api/#props) called `name` to the component.
 
 ```java
 export default {
@@ -340,7 +340,7 @@ export default {
 };
 ```
 
-Then add an [app prop](/core/contributing/components/api//#app-props) to use Pipedream managed auth with this component. For this example, we'll add an app prop for Github:
+Then add an [app prop](/core/contributing/components/api/#app-props) to use Pipedream managed auth with this component. For this example, we'll add an app prop for Github:
 
 ```javascript
 import { Octokit } from "@octokit/rest";
@@ -397,7 +397,7 @@ export default {
 };
 ```
 
-In order to help users understand what's happening with each action step, we recommend surfacing a brief summary with `$summary` ([read more](/core/contributing/components/api//#actions) about exporting data using `$.export`).
+In order to help users understand what's happening with each action step, we recommend surfacing a brief summary with `$summary` ([read more](/core/contributing/components/api/#actions) about exporting data using `$.export`).
 
 ```javascript
 import { Octokit } from "@octokit/rest";
@@ -486,6 +486,6 @@ Select an existing account or connect a new one, and then deploy your workflow a
 
 ## What's Next?
 
-You're ready to start authoring and publishing actions on Pipedream! You can also check out the [detailed component reference](/core/contributing/components/api//#component-api) at any time!
+You're ready to start authoring and publishing actions on Pipedream! You can also check out the [detailed component reference](/core/contributing/components/api/#component-api) at any time!
 
 If you have any questions or feedback, please [reach out](https://pipedream.com/community)!

docs-v2/pages/core/contributing/components/guidelines.mdx

@@ -113,7 +113,7 @@ scoped components are easier for users to understand and use.
 
 ### Required Metadata
 
-Registry [components](/core/contributing/components/api//#component-structure) require a unique
+Registry [components](/core/contributing/components/api/#component-structure) require a unique
 `key` and `version`, and a friendly `name` and `description`. Action components
 require a `type` field to be set to `action` (sources will require a type to be
 set in the future).
@@ -195,7 +195,7 @@ directory](https://github.com/PipedreamHQ/pipedream/tree/master/components).
 #### Using APIs vs Client Libraries
 
 If the app has a well-supported [Node.js client
-library](/core/contributing/components/api//#using-npm-packages), feel free to use that instead of
+library](/core/contributing/components/api/#using-npm-packages), feel free to use that instead of
 manually constructing API requests.
 
 ### `package.json`
@@ -321,7 +321,7 @@ logic should:
 #### Capturing Sensitive Data
 
 If users are required to enter sensitive data, always use
-[secret](/core/contributing/components/api//#general) props.
+[secret](/core/contributing/components/api/#general) props.
 
 ### Promoting Reusability
 
@@ -336,15 +336,15 @@ out](https://pipedream.com/community/c/dev/11).
 ##### Prop Definitions
 
 Whenever possible, reuse existing [prop
-definitions](/core/contributing/components/api//#prop-definitions-example).
+definitions](/core/contributing/components/api/#prop-definitions-example).
 
 If a prop definition does not exist and you are adding an app-specific prop that
 may be reused in future components, add it as a prop definition to the app file.
 Prop definitions will also be surfaced for apps the Pipedream marketplace.
 
 ##### Methods
 
-Whenever possible, reuse [methods](/core/contributing/components/api//#methods) defined in the app
+Whenever possible, reuse [methods](/core/contributing/components/api/#methods) defined in the app
 file. If you need to use an API for which a method is not defined and it may be
 used in future components, define a new method in the app file.
 
@@ -436,7 +436,7 @@ simply as possible.
 
 ### Labels
 
-Use [prop](/core/contributing/components/api//#user-input-props) labels to customize the name of a
+Use [prop](/core/contributing/components/api/#user-input-props) labels to customize the name of a
 prop or propDefinition (independent of the variable name in the code). The label
 should mirror the name users of an app are familiar with; i.e., it should mirror
 the equivalent label in the app’s UI. This applies to usage in labels,
@@ -445,7 +445,7 @@ but its label is set to “Search Term”.
 
 ### Descriptions
 
-Include a description for [props](/core/contributing/components/api//#user-input-props) if it helps
+Include a description for [props](/core/contributing/components/api/#user-input-props) if it helps
 the user understand what they need to do. Use Markdown as appropriate to improve
 the clarity of the description or instructions. When using Markdown:
 
@@ -474,7 +474,7 @@ Examples:
 
 ### Optional vs Required Props
 
-Use optional [props](/core/contributing/components/api//#user-input-props) whenever possible to
+Use optional [props](/core/contributing/components/api/#user-input-props) whenever possible to
 minimize the input fields required to use a component.
 
 For example, the Twitter search mentions source only requires that a user
@@ -486,7 +486,7 @@ activate the source:
 
 ### Default Values
 
-Provide [default values](/core/contributing/components/api//#user-input-props) whenever possible.
+Provide [default values](/core/contributing/components/api/#user-input-props) whenever possible.
 NOTE: the best default for a source doesn’t always map to the default
 recommended by the app. For example, Twitter defaults search results to an
 algorithm that balances recency and popularity. However, the best default for
@@ -495,15 +495,15 @@ the use case on Pipedream is recency.
 ### Async Options
 
 Avoid asking users to enter ID values. Use [async
-options](/core/contributing/components/api//#async-options-example) (with label/value definitions)
+options](/core/contributing/components/api/#async-options-example) (with label/value definitions)
 so users can make selections from a drop down menu. For example, Todoist
 identifies projects by numeric IDs (e.g., 12345). The async option to select a
 project displays the name of the project as the label, so that’s the value the
 user sees when interacting with the source (e.g., “My Project”). The code
 referencing the selection receives the numeric ID (12345).
 
 Async options should also support
-[pagination](/core/contributing/components/api//#async-options-example) (so users can navigate
+[pagination](/core/contributing/components/api/#async-options-example) (so users can navigate
 across multiple pages of options for long lists). See
 [Hubspot](https://github.com/PipedreamHQ/pipedream/blob/a9b45d8be3b84504dc22bb2748d925f0d5c1541f/components/hubspot/hubspot.app.mjs#L136)
 for an example of offset-based pagination. See
@@ -512,7 +512,7 @@ for an example of cursor-based pagination.
 
 ### Dynamic Props
 
-[Dynamic props](/core/contributing/components/api//#dynamic-props) can improve the user experience
+[Dynamic props](/core/contributing/components/api/#dynamic-props) can improve the user experience
 for components. They let you render props in Pipedream dynamically, based on the
 value of other props, and can be used to collect more specific information that
 can make it easier to use the component. See the Google Sheets example in the
@@ -521,8 +521,8 @@ linked component API docs.
 ### Interface & Service Props
 
 In the interest of consistency, use the following naming patterns when defining
-[interface](/core/contributing/components/api//#interface-props) and
-[service](/core/contributing/components/api//#service-props) props in source components:
+[interface](/core/contributing/components/api/#interface-props) and
+[service](/core/contributing/components/api/#service-props) props in source components:
 
 | Prop                | **Recommended Prop Variable Name** |
 | ------------------- | ---------------------------------- |
@@ -567,7 +567,7 @@ search criteria”.
 
 ### Emit a Summary
 
-Always [emit a summary](/core/contributing/components/api//#emit) for each event. For example, the
+Always [emit a summary](/core/contributing/components/api/#emit) for each event. For example, the
 summary for each new Tweet emitted by the Search Mentions source is the content
 of the Tweet itself.
 
@@ -576,7 +576,7 @@ format as the summary.
 
 ### Deduping
 
-Use built-in [deduping strategies](/core/contributing/components/api//#dedupe-strategies) whenever
+Use built-in [deduping strategies](/core/contributing/components/api/#dedupe-strategies) whenever
 possible (`unique`, `greatest`, `last`) vs developing custom deduping code.
 Develop custom deduping code if the existing strategies do not support the
 requirements for a source.
@@ -673,17 +673,17 @@ of just letting the error bubble up).
 
 #### Hooks
 
-[Hooks](/core/contributing/components/api//#hooks) are methods that are automatically invoked by
+[Hooks](/core/contributing/components/api/#hooks) are methods that are automatically invoked by
 Pipedream at different stages of the [component
-lifecycle](/core/contributing/components/api//#source-lifecycle). Webhook subscriptions are
+lifecycle](/core/contributing/components/api/#source-lifecycle). Webhook subscriptions are
 typically created when components are instantiated or activated via the
 `activate()` hook, and deleted when components are deactivated or deleted via
 the `deactivate()` hook.
 
 #### Helper Methods
 
 Whenever possible, create methods in the app file to manage [creating and
-deleting webhook subscriptions](/core/contributing/components/api//#hooks).
+deleting webhook subscriptions](/core/contributing/components/api/#hooks).
 
 | **Description**                         | **Method Name** |
 | --------------------------------------- | --------------- |
@@ -765,7 +765,7 @@ number of records to return.
 
 ### Use `$.summary` to Summarize What Happened
 
-[Describe what happened](/core/contributing/components/api//#returning-data-from-steps) when an
+[Describe what happened](/core/contributing/components/api/#returning-data-from-steps) when an
 action succeeds by following these guidelines:
 
 - Use plain language and provide helpful and contextually relevant information

docs-v2/pages/core/contributing/components/index.mdx

@@ -99,7 +99,7 @@ Finally, the target app must be integrated with Pipedream. You can explore all a
 
 ### Component API Reference
 
-After getting familiar with source/action development using the quickstart guides, check out [the Component API Reference](/core/contributing/components/api//) and [examples on GitHub](https://github.com/PipedreamHQ/pipedream/tree/master/components) to learn more.
+After getting familiar with source/action development using the quickstart guides, check out [the Component API Reference](/core/contributing/components/api/) and [examples on GitHub](https://github.com/PipedreamHQ/pipedream/tree/master/components) to learn more.
 
 ## Managing Privately Published Components
 

docs-v2/pages/core/contributing/components/sources-quickstart.mdx

@@ -679,6 +679,6 @@ Save and reload your source in the Pipedream UI. You should now see a countdown
 
 ## What's Next?
 
-You're ready to start authoring and deploying components on Pipedream! You can also check out the [detailed component reference](/core/contributing/components/api//) at any time!
+You're ready to start authoring and deploying components on Pipedream! You can also check out the [detailed component reference](/core/contributing/components/api/) at any time!
 
 If you have any questions or feedback, please join our [public Slack](https://pipedream.com/support).

docs-v2/pages/core/contributing/components/typescript.mdx

@@ -88,7 +88,7 @@ See [the RSS sources and actions](https://github.com/PipedreamHQ/pipedream/tree/
 
 We welcome PRs in [the `PipedreamHQ/pipedream` repo](https://github.com/PipedreamHQ/pipedream), where we store all sources and actions, the `@pipedream/types` package, these docs, and other Pipedream code. Here are a few known issues durin the **beta**:
 
-- `this` is strictly-typed within `methods`, `run`, `hooks`, and everywhere you have access to `this` in [the component API](/core/contributing/components/api//). But this typing can be improved. For example, we don't yet map props to their appropriate TypeScript type (everything is typed with `any`).
+- `this` is strictly-typed within `methods`, `run`, `hooks`, and everywhere you have access to `this` in [the component API](/core/contributing/components/api/). But this typing can be improved. For example, we don't yet map props to their appropriate TypeScript type (everything is typed with `any`).
 - The compile -> publish lifecycle hasn't been fully-automated when you're developing in the `pipedream` repo. Currently, you have to run `npm run build` from the repo root, then use the `pd` CLI to publish components after compilation. It would be nice to run `tsc-watch` and have that compile and publish the new version of the component using the `--onSuccess` flag, publishing any sources or actions accordingly.
 - We should add a linter (like `dtslint`) to all TypeScript components). Currently, `dtslint` is configured only for the `@pipedream/types` package.