Fixing link redirects

Author: Maxime Lenormand

blog/2024-09-05-dl4eo/index.mdx

@@ -98,7 +98,7 @@ _https://en.wikipedia.org/wiki/Mercator_projection_
 
 We read the content of the Pleiades image in its original projection (either the raw geometry or a transverse mercator projection in which the central meridian would pass through the center of the image). In this case, the resolution is guaranteed to be the correct native resolution of the image.
 
-The UDF gets the Pleiades image in the correct projection, then calls the prediction API, and finally returns the predictions in a GeoDataFrame which will be dynamically rendered on the map. For performance, we have added the [@fused.cache](/core-concepts/content-management/cache/) decorators which make the function automatically cache results for identical parameters. The predictions are returned in pixels in the source image and then converted into lat/long so they render on a map. Then, when we look at the result in the workbench, we get some issues at the border of the tiles.
+The UDF gets the Pleiades image in the correct projection, then calls the prediction API, and finally returns the predictions in a GeoDataFrame which will be dynamically rendered on the map. For performance, we have added the [@fused.cache](/core-concepts/cache/) decorators which make the function automatically cache results for identical parameters. The predictions are returned in pixels in the source image and then converted into lat/long so they render on a map. Then, when we look at the result in the workbench, we get some issues at the border of the tiles.
 
 import ImagePredicTileFix from '/blog/2024-09-05-dl4eo/tilingv3.png';
 

blog/2024-09-12-danieljahn/index.mdx

@@ -102,7 +102,7 @@ I'll admit, this one is a bit of a tongue-in-cheek.
 [Mapbox](https://www.mapbox.com/) is a powerful platform and Fused is not on a mission to replace it.
 
 However, it does get the point across: Fused can power a web map that obtains data from any source and processes the data on the fly as the user pans the map.
-With its [caching layer](/core-concepts/content-management/cache/), the user can get the results of previously computed locations almost instantaneously.
+With its [caching layer](/core-concepts/cache/), the user can get the results of previously computed locations almost instantaneously.
 
 Since any Fused UDF automatically serves raster and vector tiles, Fused can also be [used with Mapbox GL JS](/user-guide/out/mapbox/).
 

docs/core-concepts/data_ingestion/why-ingestion.mdx

@@ -251,7 +251,7 @@ Example of data you don't need to ingest: 50Mb `.parquet`
 
 ### Using cache as a single-use "ingester"
 
-We could actually significantly speed up the above example where we loaded the AIS data as a CSV without running `fused.ingest()`, by using [cache](/core-concepts/content-management/cache/):
+We could actually significantly speed up the above example where we loaded the AIS data as a CSV without running `fused.ingest()`, by using [cache](/core-concepts/cache/):
 
 ```python {9-13} showLineNumbers
 @fused.udf
@@ -282,7 +282,7 @@ import ImgCSVCached from '@site/docs/core-concepts/data_ingestion/cached_csv_com
 <img src={ImgCSVCached} alt="Comparing first CSV read to cached CSV read" style={{width: 600}} />
 </div>
 
-We're using [`@fused.cache`](/core-concepts/content-management/cache/) to cache the result of `load_csv()` which is the same regardless of our `bbox`, so this allows us to save an 'intermediate' result on disk. 
+We're using [`@fused.cache`](/core-concepts/cache/) to cache the result of `load_csv()` which is the same regardless of our `bbox`, so this allows us to save an 'intermediate' result on disk. 
 There are some limitations to this approach though:
 - This cache is emptied after 24h.
 - This cache is overwritten any time you change the cached function or its inputs

docs/core-concepts/write.mdx

@@ -51,7 +51,7 @@ An exception to this convention is for modules used for function annotation, whi
 
 ## `@fused.cache` decorator
 
-Use the [@fused.cache](/core-concepts/content-management/cache/) decorator to persist a function's output across runs so UDFs run faster.
+Use the [@fused.cache](/core-concepts/cache/) decorator to persist a function's output across runs so UDFs run faster.
 
 
 ```python showLineNumbers

docs/index.mdx

@@ -21,7 +21,7 @@ Fused is an end-to-end cloud platform for data analytics, build around [User Def
 To speed up Data Science pipelines we need a few things, all of which we're working on:
 - [Ingestion of data](/core-concepts/data_ingestion/) into Cloud Native formats
 - [Serverless compute engine](/core-concepts/write/) for User Defined Functions
-- [Caching of data](/core-concepts/content-management/cache/) for faster iteration & reducing cost of compute
+- [Caching of data](/core-concepts/cache/) for faster iteration & reducing cost of compute
 - [Workbench](/workbench/overview/) our browser-based IDE to develop & iterate on UDFs with a map view
 - [Batch run](/core-concepts/run-udfs/run_large/) of many User Defined Functions to scale code to any dataset size in a few lines of code
 

docs/quickstart.mdx

@@ -261,7 +261,7 @@ Now you can dive deeper into more advanced topics:
 - Take a deeper look at [Workbench](/workbench/overview/)
 - Look into the [UDF Catalog](/workbench/udf-catalog/) to find UDFs from the community you could leverage
 - Dive into the `fused` [Python SDK](/python-sdk/)
-- Learn about how [Fused handles caching](/core-concepts/content-management/cache/)
+- Learn about how [Fused handles caching](/core-concepts/cache/)
 - Join [Discord](https://bit.ly/fused-discord) to connect with the community and discover what's possible
 
 Welcome aboard! 🚢

docs/user-guide/examples/dark-vessel-detection.mdx

@@ -510,7 +510,7 @@ We've simplified the process quite a bit here, you could also:
 Before adding any new functionality, we're going to clean our UDF up a bit more:
 - Move some of the functionality into separate functions 
 - Adding common error catching (so our UDF doesn't fail if no Sentinel 1 images are found within our AOI + date range if it's too narrow)
-- Add a [cache decorator](/core-concepts/content-management/cache/) to code functions that retrieve data to speed up the UDF & reduce costs.
+- Add a [cache decorator](/core-concepts/cache/) to code functions that retrieve data to speed up the UDF & reduce costs.
 
 This will allow us to keep our UDF more readable (by abstracting code away) and more responsive. Cached functions store their result to disk, which makes a common query a lot more responsive and less expensive by using less compute