docs: fix broken links (loco-rs#841)

yinho999 · Oct 14, 2024 · 419b2e2 · 419b2e2
1 parent 93a28c2
commit 419b2e2
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/docs-site/content/docs/getting-started/guide.md b/docs-site/content/docs/getting-started/guide.md
@@ -45,7 +45,7 @@ Loco is a Web or API framework for Rust. It's also a productivity suite for deve
 
 ## Creating a New Loco App
 
-You can follow this guide for a step-by-step "bottom up" learning, or you can jump and go with the [tour](./tour.md) instead for a quicker "top down" intro.
+You can follow this guide for a step-by-step "bottom up" learning, or you can jump and go with the [tour](@/docs/getting-started/tour/index.md) instead for a quicker "top down" intro.
 
 ### Installing
 

diff --git a/docs-site/content/docs/processing/scheduler.md b/docs-site/content/docs/processing/scheduler.md
@@ -16,7 +16,7 @@ flair =[]
 +++
 
 
-Loco simplifies the traditional, often cumbersome `crontab` system, making it easier and more elegant to schedule cron jobs. The scheduler job can execute either a shell script command or run a registered [task](./task.md).
+Loco simplifies the traditional, often cumbersome `crontab` system, making it easier and more elegant to schedule cron jobs. The scheduler job can execute either a shell script command or run a registered [task](@/docs/processing/task.md).
 
 
 ## Setting Up
@@ -96,7 +96,7 @@ The scheduler configuration consists of the following elements:
         ```
     * `shell`: by default `false` meaning executing the the `run` value as a task. if `true` execute the `run` value as shell command
     * `run`: Cronjob command to run. 
-        * `Task:` The task name (with variables e.x `[TASK_NAME] KEY:VAl`. follow [here](./task.md) to see task arguments ). Note that the `shell` field should be false.
+        * `Task:` The task name (with variables e.x `[TASK_NAME] KEY:VAl`. follow [here](@/docs/processing/task.md) to see task arguments ). Note that the `shell` field should be false.
         * `Shell`: Run a shell command (e.x `"echo loco >> ./scheduler.txt"`). Note that the `shell` field should be true.
     * `tags` (Optional): A list of tags to categorize and manage the job.
     * `output` (Optional): Overrides the global `scheduler.output` for this job.