fix links

website/docs/best-practices/materializations/materializations-guide-2-available-materializations.md

@@ -9,12 +9,12 @@ hoverSnippet: Read this guide to understand the different types of materializati
 
 Views and tables and incremental models, oh my! In this section we’ll start getting our hands dirty digging into the three basic materializations that ship with dbt. They are considerably less scary and more helpful than lions, tigers, or bears — although perhaps not as cute (can data be cute? We at dbt Labs think so). We’re going to define, implement, and explore:
 
-- 🔍 **views**
-- ⚒️ **tables**
-- 📚 **incremental model**
+- 🔍 [**views**](/docs/build/materializations#view)
+- ⚒️ [**tables**](m/docs/build/materializations#table)
+- 📚 [**incremental model**](/docs/build/materializations#incremental)
 
 :::info
-👻 There is a fourth default materialization available in dbt called **ephemeral materialization**. It is less broadly applicable than the other three, and better deployed for specific use cases that require weighing some tradeoffs. We chose to leave it out of this guide and focus on the three materializations that will power 99% of your modeling needs.
+👻 There is a fourth default materialization available in dbt called [**ephemeral materialization**](/docs/build/materializations#ephemeral). It is less broadly applicable than the other three, and better deployed for specific use cases that require weighing some tradeoffs. We chose to leave it out of this guide and focus on the three materializations that will power 99% of your modeling needs.
 :::
 
 **Views and Tables are the two basic categories** of object that we can create across warehouses. They exist natively as types of objects in the warehouse, as you can see from this screenshot of Snowflake (depending on your warehouse the interface will look a little different). **Incremental models** and other materializations types are a little bit different. They tell dbt to **construct tables in a special way**.

website/docs/docs/running-a-dbt-project/using-threads.md

@@ -22,5 +22,5 @@ You will define the number of threads in your `profiles.yml` file (for dbt Core
 
 
 ## Related docs
-- [About profiles.yml](https://docs.getdbt.com/reference/profiles.yml)
+- [About profiles.yml](/docs/core/connect-data-platform/profiles.yml)
 - [dbt Cloud job scheduler](/docs/deploy/job-scheduler)

website/vercel.json

@@ -2,6 +2,11 @@
   "cleanUrls": true,
   "trailingSlash": false,
   "redirects": [
+    {
+      "source": "/reference/profiles.yml",
+      "destination": "/docs/core/connect-data-platform/profiles.yml",
+      "permanent": true
+    },
     {
       "source": "/docs/cloud/dbt-cloud-ide/dbt-cloud-tips",
       "destination": "/docs/build/dbt-tips",