From 3a41a27445d64de7b8520e4eab5f523ca3d70441 Mon Sep 17 00:00:00 2001
From: damienegan <59734022+damienegan@users.noreply.github.com>
Date: Wed, 25 Aug 2021 12:22:00 +0200
Subject: [PATCH] Fixed Vite link to https://vitejs.dev

Fixed Vite link to https://vitejs.dev
---
 docs/public/content/guide/01-cli.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/public/content/guide/01-cli.md b/docs/public/content/guide/01-cli.md
index ce075f5..046bb98 100644
--- a/docs/public/content/guide/01-cli.md
+++ b/docs/public/content/guide/01-cli.md
@@ -109,7 +109,7 @@ If you are working with another dev server, you won't need the `.js` file genera
 elm-spa gen
 ```
 
-This will generate code in the `.elm-spa` folder, but allow your custom workflow to define it's own way of compiling Elm. This is a great command to combine __elm-spa__ with another tool like [Vite](/examples/05-npm) or [Parcel](https://parceljs.org/elm.html).
+This will generate code in the `.elm-spa` folder, but allow your custom workflow to define it's own way of compiling Elm. This is a great command to combine __elm-spa__ with another tool like [Vite](https://vitejs.dev) or [Parcel](https://parceljs.org/elm.html).
 
 
 ## elm-spa watch
@@ -124,4 +124,4 @@ This will automatically generate code and compile your Elm files on save, but wi
 
 ---
 
-__Next up__: [Routing](./02-routing)
\ No newline at end of file
+__Next up__: [Routing](./02-routing)