diff --git a/packages/docs/docs/guide/rendering-videos.mdx b/packages/docs/docs/guide/rendering-videos.mdx
index 76942d12..dcdf2d4e 100644
--- a/packages/docs/docs/guide/rendering-videos.mdx
+++ b/packages/docs/docs/guide/rendering-videos.mdx
@@ -71,18 +71,18 @@ your video and subsequently merge the single parts together (for example, you
 can use 10 processes to render 1 minute of a 10-minute video each).
 
 The `renderVideo()` function
-([API reference](http://localhost:3000/renderer/renderVideo)) provides a
+([API reference](/renderer/renderVideo)) provides a
 `settings.worker` argument that you can use to parallelize rendering in a single
 process. This is useful when you have a lot of RAM available.
 
 Alternatively, the best way to set up parallelized rendering is to use
 serverless function providers like AWS Lambda. Revideo provides a
 `renderPartialVideo()` function
-([API reference](http://localhost:3000/renderer/renderPartialVideo)) that you
+([API reference](/renderer/renderPartialVideo)) that you
 can use to render a partial video - you can use it together with
 `concatenateMedia()` ([API reference](/ffmpeg/concatenateMedia)) and
 `mergeAudioWithVideo()`
-([API reference](http://localhost:3000/ffmpeg/mergeAudioWithVideo)) to
+([API reference](/ffmpeg/mergeAudioWithVideo)) to
 parallelize rendering across serverless functions. We also provide guides and
 example projects for setting up parallelized rendering on
 [AWS Lambda](https://github.com/redotvideo/examples/tree/main/parallelized-aws-lambda)