diff --git a/lure-frontend/src/routes/+page.svelte b/lure-frontend/src/routes/+page.svelte index 4fc0e29..5402705 100644 --- a/lure-frontend/src/routes/+page.svelte +++ b/lure-frontend/src/routes/+page.svelte @@ -43,7 +43,7 @@ linux-user-repository-bin and distro packages are provided at the - latest Gitea release. + latest Gitea release.

diff --git a/lure-frontend/src/routes/about/+page.svelte b/lure-frontend/src/routes/about/+page.svelte index 7b389b1..8a56e37 100644 --- a/lure-frontend/src/routes/about/+page.svelte +++ b/lure-frontend/src/routes/about/+page.svelte @@ -50,10 +50,10 @@

How does LURE keep its packages up to date?

LURE can automatically update its packages using a bot called - lure-updater. It accepts plugins - that detect when software is updated upstream and update the LURE package accordingly. The - plugins that are currently running in my instance of the bot can be found in my - updater-plugins repo. The + lure-updater. It accepts plugins that + detect when software is updated upstream and update the LURE package accordingly. The plugins + that are currently running in my instance of the bot can be found in my + updater-plugins repo. The discord-bin package, for example, checks Discord's API every hour to see if they've released an updated version, and if they have, it pushes an update to LURE's repo.