fix: shorten faq link so that it fits inside the default ptyxis width (#590)

docs/FAQ.md

@@ -98,9 +98,9 @@ For more technical detail, see [#268](https://github.com/secureblue/secureblue/i
 
 The DNSSEC setting we set in `/etc/systemd/resolved.conf.d/securedns.conf` causes known issues with network connectivity when secureblue is used in a VM. To fix it, comment out `DNSSEC=allow-downgrade` in that file and manually set a dns provider in network settings.
 
-#### Release notifications
+#### Releases
 
-On the secureblue github page, click "Watch", and then "Custom", and select Releases like so:
+To subscribe to release notifications, on the secureblue github page, click "Watch", and then "Custom", and select Releases like so:
 
 ![image](https://github.com/user-attachments/assets/38146394-f730-4b84-8bfa-4fbbf29350ff)
 

docs/POSTINSTALL-README.md

@@ -4,7 +4,7 @@ After rebasing to secureblue, follow the following steps in order.
 
 ## Subscribe to secureblue release notifications
 
-[FAQ](FAQ.md#release-notifications)
+[FAQ](FAQ.md#releases)
 
 ## Nvidia
 If you are using an nvidia image, run this after installation:

files/system/usr/libexec/ublue-motd

@@ -29,7 +29,7 @@ elif [ "$IMAGE_TAG" != "latest" ]; then
 elif [ "$DIFFERENCE" -ge "$WEEK" ]; then
     TIP='**Your current image is over 1 week old, run `ujust update`.**'
 else
-    TIP='**For secureblue release notifications,** [subscribe:](https://github.com/secureblue/secureblue/blob/live/FAQ.md#release-notifications)'
+    TIP='**For secureblue release notifications,** [subscribe:](https://github.com/secureblue/secureblue/blob/live/docs/FAQ.md#releases)'
 fi
 
 sed -e "s/%IMAGE_REF_NAME%/$IMAGE_REF_NAME/g" -e "s/%IMAGE_TAG%/$IMAGE_TAG/g" -e "s|%TIP%|$TIP|g" /usr/share/ublue-os/motd/secureblue.md | tr '~' '\n' | glow -s auto -w 78 -