fix links (#14153)

docs/3.0rc/deploy/serve-flows/deploy-a-flow.mdx

@@ -353,7 +353,7 @@ def main():
 **Using the Prefect client**
 
 For more information on using the Prefect client to interact with Prefect's
-REST API, see [Interact with the API](/3.0rc/manage/cloud/interact-with-api/).
+REST API, see [Interact with the API](/3.0rc/manage/interact-with-api/).
 </Tip>
 
 ## Versioning and bookkeeping

docs/3.0rc/deploy/work-pools/control-runs.mdx

@@ -539,7 +539,7 @@ Below is a list of available worker types. Most worker types require installatio
 | [`azure-container-instance`](https://prefecthq.github.io/prefect-azure/container_instance_worker/) | Execute flow runs in ACI containers | `prefect-azure` |
 
 If you don’t see a worker type that meets your needs, consider 
-[developing a new worker type](/3.0rc/guides/deployment/developing-a-new-worker-type/).
+[developing a new worker type](/contribute/develop-a-new-worker-type/).
 
 ### Worker options
 

docs/3.0rc/develop/connect-third-party.mdx

@@ -155,10 +155,6 @@ Create a new `S3Bucket` by setting the `name` parameter to a new value:
 new_bucket_block.save(name="my-new-data-bucket-block")
 ```
 
-<Tip>
-You can also create and update blocks through the [Prefect UI](/3.0rc/manage/cloud/blocks/).
-</Tip>
-
 ### Load blocks
 
 You can use the block name to load the block:

docs/3.0rc/develop/interact-with-data.mdx

@@ -8,7 +8,7 @@ Learn how to use Prefect to move data to and from AWS, Azure, and GCP blob stora
 ## Prerequisites
 
 - Prefect [installed](/3.0rc/get-started/install/)
-- Authenticated with [Prefect Cloud](/3.0rc/manage/cloud/cloud-quickstart/) (or self-hosted 
+- Authenticated with [Prefect Cloud](/3.0rc/manage/cloud/connect-to-cloud/) (or self-hosted 
 [Prefect server](/3.0rc/manage/self-host/) instance)
 - A cloud provider account
 

docs/3.0rc/develop/observe-workflows/logging.mdx

@@ -4,7 +4,7 @@ description: Capture fine-grained information about flows and tasks for monitori
 ---
 
 Prefect captures logs for your flow and task runs by default, even if you have not started a 
-Prefect server with `prefect server start`. View and filter logs in the [UI](/3.0rc/manage/cloud/flow-runs/#inspect-a-flow-run) or 
+Prefect server with `prefect server start`. View and filter logs in the UI or 
 access log records through the API.
 
 When you run a flow, Prefect automatically logs events for flow runs and task runs, along with any custom 
@@ -27,7 +27,7 @@ Completed('All states completed.')
 ```
 </div>
 
-See logs for a flow run in the UI by navigating to the [**Flow runs**](/3.0rc/manage/cloud/flow-runs/#inspect-a-flow-run) 
+See logs for a flow run in the UI by navigating to the **Flow runs** 
 page and selecting a specific flow run to inspect.
 
 ![Viewing logs for a flow run in the Prefect UI](/3.0rc/img/ui/flow-run-details.png)

docs/3.0rc/develop/write-tasks/upstream-dependencies.mdx

@@ -151,10 +151,8 @@ def final_task(input):
     print(input)
 ```
 
-<figure markdown="span">
-  ![Flow run graph for automatic task dependencies](/3.0rc/img/guides/automatic-task-dependencies.png)
-  <figcaption>Flow run graph displaying inferred dependencies with the "Dependency grid" layout selected</figcaption>
-</figure>
+![Flow run graph for automatic task dependencies](/3.0rc/img/guides/automatic-task-dependencies.png)
+<figcaption>Flow run graph displaying inferred dependencies with the "Dependency grid" layout selected</figcaption>
 
 
 ### Manual

docs/3.0rc/get-started/index.mdx

@@ -16,7 +16,7 @@ With Prefect you gain:
 * [Convenient async functionality](/3.0rc/develop/write-tasks/use-task-runners/#task-runners)
 * [Caching](/3.0rc/develop/write-tasks/index#caching)
 * [Notifications](/3.0rc/react/events/automations-triggers/)
-* [Observability](/3.0rc/manage/cloud/connect-to-cloud/index)
+* [Observability](/3.0rc/develop/observe-workflows/index/)
 * [Event-based orchestration](/3.0rc/react/events/webhook-triggers)
 
 ![screenshot of Prefect Cloud dashboard](/3.0rc/img/ui/cloud-dashboard.png)

docs/3.0rc/get-started/install.mdx

@@ -21,7 +21,7 @@ This command also installs or upgrades Prefect's Python dependencies.
 
 Learn more about release versions in the [Prefect Release Notes](https://github.com/PrefectHQ/prefect/blob/main/RELEASE-NOTES.md).
 
-See our [Contributing guide](3.0rc/community/install-contribute) for instructions on installing Prefect for development.
+See our [Contributing guide](/contribute/install-contribute/) for instructions on installing Prefect for development.
 
 ## Check your installation
 

docs/3.0rc/get-started/quickstart.mdx

@@ -149,7 +149,7 @@ A [work pool](/3.0rc/deploy/work-pools/control-runs/) is the most common way to
   <Tab title="Prefect Cloud">
 Deploy your flow to Cloud using a managed work pool.
 
-1. Create a [managed work pool](/3.0rc/deploy/serve-flows/index):
+1. Create a [managed work pool](/3.0rc/deploy/work-pools/control-runs):
 
    ```bash
    prefect work-pool create my-work-pool --type prefect:managed

docs/3.0rc/manage/configure-client.mdx

@@ -29,7 +29,7 @@ See [Configuring settings](#configuring-settings) for details on setting and uns
 
 ### PREFECT_API_KEY
 
-The `PREFECT_API_KEY` value specifies the [API key](/3.0rc/manage/cloud/cloud-api-keys/#create-an-api-key) used to authenticate with Prefect Cloud.
+The `PREFECT_API_KEY` value specifies the [API key](/3.0rc/manage/cloud/manage-users/api-keys/) used to authenticate with Prefect Cloud.
 
 ```bash
 PREFECT_API_KEY="[API-KEY]"

docs/3.0rc/resources/big-data.mdx

@@ -106,7 +106,7 @@ cloud provider.
 
 Caching saves you time and compute by allowing you to avoid re-running tasks unnecessarily.
 Note that caching requires task result persistence.
-Learn more about [caching](/3.0rc/develop/write-tasks.md/#caching).
+Learn more about [caching](/3.0rc/develop/write-tasks/index/).
 
 ### Compress results written to disk