diff --git a/How-to-convert-video-with-VERT.md b/How-to-convert-video-with-VERT.md
index 45f78d8..e75b226 100644
--- a/How-to-convert-video-with-VERT.md
+++ b/How-to-convert-video-with-VERT.md
@@ -1,4 +1,4 @@
-Unlike image and audio conversion, video conversion is hard to do in a browser, because it uses a lot of resources, and will end up running _very_ slowly (if it even works at all).
+On VERT, video uploads to a server for processing by default. This is because video conversion is hard to do in a browser as it uses a lot of resources, and will end up running _very_ slowly (if it even works at all).
 
 Our answer to this is [`vertd`](https://github.com/VERT-sh/vertd), which is a simple FFmpeg wrapper built in Rust. If you don't understand all that technical jargon, **it basically allows you to convert videos using the full capacity of your computer**, which results in much faster conversion. It runs on your computer (or a server somewhere, if you know what you're doing), and the VERT web interface reaches out to it in order to convert your videos.
 
@@ -6,4 +6,4 @@ We host an official instance of [`vertd`](https://github.com/VERT-sh/vertd) so y
 - Download the latest release of `vertd` for your machine [here](https://github.com/VERT-sh/vertd/releases)
 - Run the server
 - Connect the VERT UI to your local `vertd` instance by entering its IP & port
-  - By default, `vertd` runs a HTTP server on port `24153`, so you would put `http://localhost:24153` in the "Instance URL" setting found in VERT's settings
\ No newline at end of file
+  - By default, `vertd` runs a HTTP server on port `24153`, so you would put `http://localhost:24153` in the "Instance URL" setting found in VERT's settings (assuming you are running it on your own PC)
\ No newline at end of file