@ -11,7 +11,7 @@ These schedules do not trigger Kometa to run; they control what Kometa will do i
time. `weekly(sunday)`, for example, does not mean "run Kometa on Sunday to do this thing"; it means "If Kometa is running,
time. `weekly(sunday)`, for example, does not mean "run Kometa on Sunday to do this thing"; it means "If Kometa is running,
and it's Sunday, do this thing".
and it's Sunday, do this thing".
If you want to control when Kometa itself runs, like if you want Kometa to only run on Tuesdays and Thursdays, see [this page](../kometa/scheduling.md).
If you want to control when Kometa itself runs, like if you want Kometa to only run on Tuesdays and Thursdays, see [this page](../kometa/guides/scheduling.md).
@ -17,7 +17,7 @@ Instead, it is recommended to set an automated scheduling service so that Kometa
This page discusses how to set up this "When should Kometa run" level of schedule, and it leverages both the "modes" of running discussed above.
This page discusses how to set up this "When should Kometa run" level of schedule, and it leverages both the "modes" of running discussed above.
**You can also put schedule information in your config to control things like "process the Movie library only on Tuesdays" or the like. That level of scheduling is independent of when Kometa runs, and is discussed [here](../../config/schedule.md)**
**You can also put schedule information in your config to control things like "process the Movie library only on Tuesdays" or the like. That level of scheduling is configured independently fromthe "when Kometa runs" scheduling covered on this page, and is discussed [here](../../config/schedule.md)**
IMPORTANT: Every time you see `/path/to` below, it's a placeholder for the path to that directory on *your* system.
IMPORTANT: Every time you see `/path/to` below, it's a placeholder for the path to that directory on *your* system.