From 6f290623d457bfa361c5e7a877d166566141aff6 Mon Sep 17 00:00:00 2001
From: Floo <21978691+floo-one@users.noreply.github.com>
Date: Fri, 23 Aug 2024 18:30:35 +0200
Subject: [PATCH] Update rendering-videos.mdx

removed localhost links
---
 packages/docs/docs/guide/rendering-videos.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/packages/docs/docs/guide/rendering-videos.mdx b/packages/docs/docs/guide/rendering-videos.mdx
index 76942d124..dcdf2d4e5 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)