fix http urls

Author: andrewjschuang

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

@@ -52,7 +52,7 @@ Download the appropriate [Linux CLI build](#cli-builds) for your architecture. U
 
 ## CLI Builds
 
-Pipedream publishes the following builds of the CLI. If you need to use the CLI on another OS or architecture, [please reach out](https://docs.pipedream.com/support/).
+Pipedream publishes the following builds of the CLI. If you need to use the CLI on another OS or architecture, [please reach out](https://pipedream.com/support/).
 
 | Operating System | Architecture | link                                                              |
 | ---------------- | ------------ | ----------------------------------------------------------------- |

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

@@ -1026,7 +1026,7 @@ pd deploy my-source.js
 
 ##### From Pipedream Github Repo
 
-You can explore the components available to deploy in [Pipedream's GitHub repo](https://github.com/pipedreamhq/pipedream/tree/master/components).
+You can explore the components available to deploy in [Pipedream's GitHub repo](https://github.com/PipedreamHQ/pipedream/tree/master/components).
 
 ```bash
 pd deploy <source-key>

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

@@ -107,7 +107,7 @@ filters events for only new star activity so the user doesn't have to.
 
 There may be cases where it's valuable to create a generic component that
 provides users with broad latitude (e.g., see the [custom
-webhook](https://github.com/pipedreamhq/pipedream/blob/master/components/github/sources/custom-webhook-events)
+webhook](https://github.com/PipedreamHQ/pipedream/blob/master/components/github/sources/custom-webhook-events)
 event source for GitHub). However, as a general heuristic, we found that tightly
 scoped components are easier for users to understand and use.
 
@@ -190,7 +190,7 @@ Registry components are organized by app in the `components` directory of the
   (-) (i.e., in kebab case)
 
 You can explore examples in the [components
-directory](https://github.com/pipedreamhq/pipedream/tree/master/components).
+directory](https://github.com/PipedreamHQ/pipedream/tree/master/components).
 
 #### Using APIs vs Client Libraries
 

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

@@ -7,7 +7,7 @@ import VideoPlayer from '@/components/VideoPlayer'
 
 Components are [Node.js modules](api/#component-structure) that run on Pipedream's serverless infrastructure. They can use Pipedream managed auth for [{process.env.PUBLIC_APPS}+ apps](https://pipedream.com/explore) (for both OAuth and key-based APIs) and [use most npm packages](api/#using-npm-packages) with no `npm install` or `package.json` required.
 
-Components are most commonly used as the building blocks of Pipedream workflows, but they can also be used like typical serverless functions. You can explore curated components for popular apps in Pipedream's [Marketplace](https://pipedream.com/explore) and [GitHub repo](https://github.com/pipedreamhq/pipedream/tree/master/components) or you can author and share your own.
+Components are most commonly used as the building blocks of Pipedream workflows, but they can also be used like typical serverless functions. You can explore curated components for popular apps in Pipedream's [Marketplace](https://pipedream.com/explore) and [GitHub repo](https://github.com/PipedreamHQ/pipedream/tree/master/components) or you can author and share your own.
 
 <Callout type="info">
 Our TypeScript component API is in **beta**. If you're interested in developing TypeScript components and providing feedback, [see our TypeScript docs](/core/contributing/components/typescript/).
@@ -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/typescript.mdx

@@ -14,7 +14,7 @@ During the beta, the `@pipedream/types` package and other TypeScript configurati
 
 ## Why TypeScript?
 
-Most Pipedream components in [the registry](https://github.com/PipedreamHQ/pipedream/) are written in Node.js. Writing components in TypeScript can reduce bugs and speed up development, with very few changes to your code.
+Most Pipedream components in [the registry](https://github.com/PipedreamHQ/pipedream) are written in Node.js. Writing components in TypeScript can reduce bugs and speed up development, with very few changes to your code.
 
 If you haven't written TypeScript, start with [this tutorial](https://www.typescriptlang.org/docs/handbook/typescript-from-scratch.html).
 
@@ -26,7 +26,7 @@ If you've never developed Pipedream components before, [start here](/core/contri
 
 ### Developing TypeScript components in the `PipedreamHQ/pipedream` registry
 
-1. [Fork and clone the repo](https://github.com/PipedreamHQ/pipedream/).
+1. [Fork and clone the repo](https://github.com/PipedreamHQ/pipedream).
 
 2. Run `pnpm install` to install dependencies.
 

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

@@ -3,9 +3,9 @@ import { FileTree } from 'nextra/components'
 
 # Pipedream Registry
 
-When developing workflows with pre-built actions and triggers, under the hood you're using [components](/core/contributing/components/) from the [Pipedream Registry Github Repository](https://github.com/pipedreamhq/pipedream).
+When developing workflows with pre-built actions and triggers, under the hood you're using [components](/core/contributing/components/) from the [Pipedream Registry Github Repository](https://github.com/PipedreamHQ/pipedream).
 
-Components contributed to the [Pipedream Registry Github Repository](https://github.com/pipedreamhq/pipedream) are published to the [Pipedream marketplace](https://pipedream.com/apps) and are listed in
+Components contributed to the [Pipedream Registry Github Repository](https://github.com/PipedreamHQ/pipedream) are published to the [Pipedream marketplace](https://pipedream.com/apps) and are listed in
 the Pipedream UI when building workflows.
 
 <Callout type="info">
@@ -58,7 +58,7 @@ Anyone from the community can build [sources](/core/workflows/triggers/) and [ac
 
 To submit new components or update existing components:
 
-1. Fork the public [Pipedream Registry Github Repository](https://github.com/pipedreamhq/pipedream).
+1. Fork the public [Pipedream Registry Github Repository](https://github.com/PipedreamHQ/pipedream).
 2. Create a new component within the corresponding app's directory within the `components` directory (if applicable).
 3. [Create a PR for the Pipedream team to review](https://github.com/PipedreamHQ/pipedream/compare).
 4. Address any feedback provided by Pipedream based on the best practice [Component Guidelines & Patterns](/core/contributing/components/guidelines/).
@@ -85,15 +85,15 @@ actions for Pipedream's registry.
 
 | Name                                                                                                                                                          | App          | Type                                         |
 | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | -------------------------------------------- |
-| [New Card](https://github.com/pipedreamhq/pipedream/blob/master/components/trello/sources/new-card/new-card.mjs)                                              | Trello       | Webhook                                      |
-| [New or Modified Files](https://github.com/pipedreamhq/pipedream/blob/master/components/google_drive/sources/new-or-modified-files/new-or-modified-files.mjs) | Google Drive | Webhook + Polling                            |
-| [New Submission](https://github.com/pipedreamhq/pipedream/blob/master/components/jotform/sources/new-submission/new-submission.mjs)                           | Jotform      | Webhook (with no unique hook ID)             |
+| [New Card](https://github.com/PipedreamHQ/pipedream/blob/master/components/trello/sources/new-card/new-card.mjs)                                              | Trello       | Webhook                                      |
+| [New or Modified Files](https://github.com/PipedreamHQ/pipedream/blob/master/components/google_drive/sources/new-or-modified-files/new-or-modified-files.mjs) | Google Drive | Webhook + Polling                            |
+| [New Submission](https://github.com/PipedreamHQ/pipedream/blob/master/components/jotform/sources/new-submission/new-submission.mjs)                           | Jotform      | Webhook (with no unique hook ID)             |
 
 ### Reference Actions
 
 | Name                                                                                                                                                  | App           |
 | ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- |
 | [Add Multiple Rows](https://github.com/PipedreamHQ/pipedream/blob/master/components/google_sheets/actions/add-multiple-rows/add-multiple-rows.mjs)    | Google Sheets |
-| [Send Message](https://github.com/PipedreamHQ/pipedream/blob/master/components/discord_webhook/actions/send-message/send-message.mjs)                 | Discord       |
+| [Send Message](https://github.com/PipedreamHQ/pipedream/blob/master/components/discord_bot/actions/send-message/send-message.mjs)                 | Discord       |
 | [Append Text](https://github.com/PipedreamHQ/pipedream/blob/master/components/google_docs/actions/append-text/append-text.mjs)                        | Google Docs   |
 | [`GET` request](https://github.com/PipedreamHQ/pipedream/blob/master/components/http/actions/get-request/get-request.mjs)                             | HTTP          |

docs-v2/pages/core/environment-variables.mdx

@@ -115,7 +115,7 @@ You can reference the value of environment variables using `{{process.env.YOUR_E
 />
 
 <Callout type="info">
-  [Private components](https://pipedream.com/docs/workflows/contributing/components#using-components) (actions or triggers) do not have direct access to workspace or project variables as public components or code steps. Add a prop specifically for the variable you need. For sensitive data like API keys, [configure the prop as a secret](https://pipedream.com/docs/workflows/contributing/components/api#props). In your prop configuration, set the value to `{{process.env.YOUR_ENV_VAR}}` to securely reference the environment variable.
+  [Private components](/core/contributing/components/#using-components) (actions or triggers) do not have direct access to workspace or project variables as public components or code steps. Add a prop specifically for the variable you need. For sensitive data like API keys, [configure the prop as a secret](/core/contributing/components/api/#props). In your prop configuration, set the value to `{{process.env.YOUR_ENV_VAR}}` to securely reference the environment variable.
 </Callout>
 
 ## Frequently Asked Questions

docs-v2/pages/core/event-history.mdx

@@ -4,7 +4,7 @@ import ArcadeEmbed from '@/components/ArcadeEmbed'
 
 # Event History
 
-Monitor all workflow events and their stack traces in one centralized view under the [**Event History**](https://pipedream.com/workflows/event-history) section in the dashboard.
+Monitor all workflow events and their stack traces in one centralized view under the [**Event History**](https://pipedream.com/event-history) section in the dashboard.
 
 Within the **Event History**, you'll be able to filter your events by workflow, execution status, within a specific time range.
 

docs-v2/pages/core/git.mdx

@@ -195,9 +195,9 @@ Yes, you can use the GitHub Syncing feature to develop your workflows from YAML
 Then pushing changes to the `production` branch will trigger a deploy for your Pipedream workflows.
 
 ### Why am I seeing the error "could not resolve step[index].uses: component-key@version" when merging to production?
-This error occurs when a workflow references a [private component](https://pipedream.com/docs/workflows/contributing/components#using-private-actions) without properly prefixing the component key with your workspace name in the `workflow.yaml` configuration file. Pipedream requires this prefix to correctly identify and resolve components specific to your workspace.
+This error occurs when a workflow references a [private component](/core/contributing/components/#using-private-actions) without properly prefixing the component key with your workspace name in the `workflow.yaml` configuration file. Pipedream requires this prefix to correctly identify and resolve components specific to your workspace.
 
-For example, if you modified a [registry action](https://pipedream.com/docs/apps/contributing) and published it privately, the correct component key should be formatted as `@workspacename/component-key@version` (e.g., `@pipedream/[email protected]`).
+For example, if you modified a [registry action](/core/contributing/) and published it privately, the correct component key should be formatted as `@workspacename/component-key@version` (e.g., `@pipedream/[email protected]`).
 
 To resolve this error:
 
@@ -206,7 +206,7 @@ To resolve this error:
 3. Add your workspace name prefix to the component key, ensuring it follows the format `@workspacename/component-key@version`.
 4. Commit your changes and push them to your repository.
 5. Open your project in the Pipedream UI and select your development branch.
-6. Click on **Merge to Production** and verify the deployment success in the [Changelog](https://pipedream.com/docs/workflows/git#use-the-changelog).
+6. Click on **Merge to Production** and verify the deployment success in the [Changelog](/core/git/#use-the-changelog).
 7. If the issue persists, [reach out to Pipedream Support](https://pipedream.com/support) for further assistance.
 
 ### Why am I seeing an error about "private auth mismatch" when trying to merge a branch to production?

docs-v2/pages/core/projects/access-controls.mdx

@@ -24,7 +24,7 @@ Workspace owners and admins are able to perform all actions in projects, whereas
 | Operation                                                    | Project creator | Workspace members |
 | ------------------------------------------------------------ | :-------------: | :---------------: |
 | View in [projects listing](https://pipedream.com/projects)   |       ✅        |        ✅         |
-| View in [Event History](https://pipedream.com/workflows/event-history) |       ✅        |        ✅         |
+| View in [Event History](https://pipedream.com/event-history) |       ✅        |        ✅         |
 | View in global search                                        |       ✅        |        ✅         |
 | Manage project workflows                                     |       ✅        |        ✅         |
 | Manage project files                                         |       ✅        |        ✅         |