Fixing links

Author: dannyroosevelt

docs-v2/pages/account/billing-settings.mdx

@@ -6,38 +6,40 @@ You'll find information on your usage data (for specific [Pipedream limits](/wor
 
 ## Subscription
 
-You can upgrade to [paid plans](https://pipedream.com/pricing) from this section.
-
 If you've already upgraded, you'll see an option to **Manage Subscription** here, which directs you to your personal Stripe portal. Here, you can change your payment method, review the details of previous invoices, and more.
 
 ## Usage
 
-[Credits](/pricing/#credits) are Pipedream's billable unit, and users on the [free tier](/pricing/#free-tier) are limited on the number of daily free credits allocated. The **Usage** section displays a chart of the daily credits across a historical range of time to provide insight into your usage patterns.
+[Credits](/pricing/#credits-and-billing) are Pipedream's billable unit, and users on the [free plan](/pricing/#free-plan) are limited on the number of daily free credits allocated. The **Usage** section displays a chart of the daily credits across a historical range of time to provide insight into your usage patterns.
+
+<Callout type="warning">
+Credit usage from [Connect](/connect) is not yet reflected in this section.
+</Callout>
 
 Hover over a specific column in the chart to see the number of credits run for that specific day:
 
 ![Daily credits tooltip](/images/account/daily-invocations-tooltip.png)
 
-_Click_ on a specific column to see credits for that day, broken out by workflow / source:
+Click on a specific column to see credits for that day, broken out by workflow / source:
 
 ![Credits broken out by workflow / source](/images/account/usage-by-resource.png)
 
 Users on the free tier will see the last 30 days of usage in this chart. Users on [paid plans](https://pipedream.com/pricing) will see the cumulative usage tied to their current billing period.
 
 ## Compute Budget
 
-Control the maximum number of compute credits permitted on your account with an _Credit Budget_.
+Control the maximum number of credits permitted on your account with a **Credit Budget**.
 
-This will restrict your account-wide usage to the specified number of [credits](/pricing/#credits) on a monthly or daily basis. The compute budget does not apply to credits incurred by [dedicated workers](/workflows/building-workflows/settings/#eliminate-cold-starts).
+This will restrict your workspace-wide usage to the specified number of [credits](/pricing/#credits-and-billing) on a monthly or daily basis. The compute budget does not apply to credits incurred by [dedicated workers](/workflows/building-workflows/settings/#eliminate-cold-starts) or Pipedream Connect.
 
-To enable this feature, _click_ on the toggle and define your maximum number of credits in the period.
+To enable this feature, click on the toggle and define your maximum number of credits in the period.
 
 <Callout type="info">
-Due to how credits are accrued, there may be cases where your credit usage may _slightly_ go over the cap.
+Due to how credits are accrued, there may be cases where your credit usage may go slightly over the cap.
 
 In an example scenario, with a cap set at 20 credits and a long-running workflow that uses 10 credits per run, it's possible that two concurrent events trigger the workflow, and the cap won't apply until after the concurrent events are processed.
 </Callout>
 
 ## Limits
 
-For users on the [Free tier](/pricing/#free-tier), this section displays your usage towards your [credits quota](/workflows/limits/#daily-credits-limit) for the current UTC day.
+For users on the [Free tier](/pricing/#free-plan), this section displays your usage towards your [credits quota](/workflows/limits/#daily-credits-limit) for the current UTC day.

docs-v2/pages/connect/api.mdx

@@ -235,10 +235,6 @@ curl -X POST "https://api.pipedream.com/v1/connect/{your_project_id}/actions/run
 
 ## API Reference
 
-### Invoke workflows
-
-You can use the SDK to [invoke workflows on behalf of any end user](/connect/workflows/). **Write one workflow, run it for all of your users**.
-
 ### Tokens
 
 Your app will initiate the account connection flow for your end users in your frontend. To securely scope connection to a specific end user, on your server, **you retrieve a short-lived token for that user**, and return that token to your frontend.
@@ -3726,3 +3722,9 @@ curl -X PUT \
   ]
 }
 ```
+
+### Workflows
+
+#### Invoke workflows
+
+You can use the SDK to [invoke workflows on behalf of any end user](/connect/workflows/). **Write one workflow, run it for all of your users**.

docs-v2/pages/glossary.mdx

@@ -104,7 +104,7 @@ You can restrict access to connected accounts to specific individuals or share w
 
 ### Credit
 
-Pipedream charges one credit per 30 seconds of compute time at 256MB megabytes of memory (the default) per workflow execution. Credits are also charged for [dedicated workers](#dedicated-workers). [See the docs](/pricing/#credits) for more details.
+Pipedream charges one credit per 30 seconds of compute time at 256MB megabytes of memory (the default) per workflow execution. Credits are also charged for [dedicated workers](#dedicated-workers). [See the docs](/pricing/#credits-and-billing) for more details.
 
 ### Custom domain
 

docs-v2/pages/pricing/index.mdx

@@ -110,7 +110,7 @@ If an active workflow isn't executed in a billing period no credit usage is incu
 
 #### Source credit usage
 
-When an [event source](/workflows/building-workflows/triggers/) triggers a workflow, **the source execution is included for free.** This includes workspaces on the [Free Tier](/pricing/#free-tier).
+When an [event source](/workflows/building-workflows/triggers/) triggers a workflow, **the source execution is included for free.** This includes workspaces on the [Free plan](/pricing/#free-plan).
 
 When a source is configured as a workflow trigger, the core value is in the workflow. You won't be charged for two credits (one to run the source, one to run the workflow) when the workflow contains the core logic.
 

docs-v2/pages/workflows/building-workflows/code/nodejs/delay.mdx

@@ -53,7 +53,7 @@ One credit is used to initially start the workflow, then the second credit is us
 <Callout type="info">
 Exact credit usage depends on duration and memory configuration
 
-If your workflow's [execution timeout limit](/workflows/building-workflows/settings/#execution-timeout-limit) is set to longer than [default limit](/workflows/limits/#time-per-execution), it may incur more than two [credits](/pricing/#credits) when using `pd.flow.delay`.
+If your workflow's [execution timeout limit](/workflows/building-workflows/settings/#execution-timeout-limit) is set to longer than [default limit](/workflows/limits/#time-per-execution), it may incur more than two [credits](/pricing/#credits-and-billing) when using `pd.flow.delay`.
 </Callout>
 
 ## `cancel_url` and `resume_url`

docs-v2/pages/workflows/building-workflows/code/nodejs/rerun.mdx

@@ -256,7 +256,7 @@ These functions will only suspend and resume when run in production.
 
 ## Credits when using `suspend` / `rerun`
 
-You are not charged for the time your workflow is suspended during a `$.flow.rerun` or `$.flow.suspend`. Only when workflows are resumed will compute time count toward [credit usage](/pricing/#credits).
+You are not charged for the time your workflow is suspended during a `$.flow.rerun` or `$.flow.suspend`. Only when workflows are resumed will compute time count toward [credit usage](/pricing/#credits-and-billing).
 
 <Callout type="warning">
 When a suspended workflow reawakens, it will reset the credit counter.

docs-v2/pages/workflows/building-workflows/code/python/delay.mdx

@@ -51,7 +51,7 @@ One credit is used to initially start the workflow, then the second credit is us
 <Callout type="info">
 Exact credit usage depends on duration and memory configuration
 
-If your workflow's [execution timeout limit](/workflows/building-workflows/settings/#execution-timeout-limit) is set to longer than [default limit](/workflows/limits/#time-per-execution), it may incur more than two [credits](/pricing/#credits) when using `pd.flow.delay`.
+If your workflow's [execution timeout limit](/workflows/building-workflows/settings/#execution-timeout-limit) is set to longer than [default limit](/workflows/limits/#time-per-execution), it may incur more than two [credits](/pricing/#credits-and-billing) when using `pd.flow.delay`.
 </Callout>
 
 ## `cancel_url` and `resume_url`

docs-v2/pages/workflows/building-workflows/code/python/rerun.mdx

@@ -170,7 +170,7 @@ These functions will only suspend and resume when run in production.
 
 ## Credits usage when using `pd.flow.suspend` / `pd.flow.rerun`
 
-You are not charged for the time your workflow is suspended during a `pd.flow.suspend` or `pd.flow.rerun`. Only when workflows are resumed will compute time count toward [credit usage](/pricing/#credits).
+You are not charged for the time your workflow is suspended during a `pd.flow.suspend` or `pd.flow.rerun`. Only when workflows are resumed will compute time count toward [credit usage](/pricing/#credits-and-billing).
 
 <Callout type="warning">
 When a suspended workflow reawakens, it will reset the credit counter.

docs-v2/pages/workflows/building-workflows/sharing.mdx

@@ -131,7 +131,7 @@ Sharing workflows via link is available on all plans, including the Free tier pl
 
 To copy a workflow, a subscription is not required. However, the copied workflow is subject to the current workspace's plan limits.
 
-For example, if a workflow requires more connected accounts than what's available on the [Free tier](/pricing/#free-tier), then users of your workflow will require a plan to run the workflow properly.
+For example, if a workflow requires more connected accounts than what's available on the [Free tier](/pricing/#free-plan), then users of your workflow will require a plan to run the workflow properly.
 
 ### Will copies of my workflow use my credits?