docs

Author: userdocs

docs/package-lock.json

@@ -10,9 +10,9 @@
 		"astro": "astro"
 	},
 	"dependencies": {
-		"@astrojs/starlight": "^0.31.1",
+		"@astrojs/starlight": "^0.32.0",
 		"@expressive-code/plugin-collapsible-sections": "^0.40.0",
-		"astro": "^5.2.5",
+		"astro": "^5.3.0",
 		"expressive-code": "^0.40.0",
 		"gray-matter": "^4.0.3",
 		"sharp": "^0.32.5",

docs/package.json

@@ -9,9 +9,11 @@ import { Advanced, BuildInfo, Charts, Details, Modal, Steps, Tabs, TabItem, Card
 
 `qbittorrent-nox-static.sh™` was originally a simple, amateurish bash script, to build a static `qbittorrent-nox` binary for `x86_64`. The script has grown and evolved since then and now it's a complicated bash script.
 
-As of `02/2025`: `qbt-nox-static.bash™` is `v2.1.1` and `qbittorrent-nox-static.sh™` is `v2.0.16`. The former is a fork of the latter, from this version, with changes specific to the dependency handling, which in turn makes breaking changes to the default behaviour of the script. Combined with renaming the script to `.bash` from `.sh` as it is not a POSIX compliant script this would effectively have made `qbittorrent-nox-static.sh` unavailable for use.
+:::note
+`qbt-nox-static.bash™` is `v2.1.1` and `qbittorrent-nox-static.sh™` is `v2.0.16`. The former is a fork of the latter, from this version, with changes specific to the dependency handling, which in turn makes breaking changes to the default behavior of the script. Combined with renaming the script to `.bash` from `.sh` as it is not a POSIX compliant script this would effectively have made `qbittorrent-nox-static.sh` unavailable for use.
 
 So the existence of the two is a transitional change and the `qbittorrent-nox-static.sh` will be deprecated in the future, though any non breaking changes will be backported to the original script.
+:::
 
 ### What does it do?