upgpkg: homebridge-config-ui-x 4.55.1-5

* Packaging bugfix

3 files changed, 4 insertions, 4 deletions

diff --git a/.SRCINFO b/.SRCINFO
index 9fbc382ad206..d006846ea369 100644
--- a/.SRCINFO
+++ b/.SRCINFO
@@ -1,7 +1,7 @@
 pkgbase = homebridge-config-ui-x
 	pkgdesc = Web-based management tool for Homebridge
 	pkgver = 4.55.1
-	pkgrel = 4
+	pkgrel = 5
 	url = https://github.com/oznu/homebridge-config-ui-x
 	install = homebridge-config-ui-x.install
 	arch = any
diff --git a/PKGBUILD b/PKGBUILD
index 44e7f64a12d4..e6fea64f3164 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -3,7 +3,7 @@
 
 pkgname=homebridge-config-ui-x
 pkgver=4.55.1
-pkgrel=4
+pkgrel=5
 pkgdesc='Web-based management tool for Homebridge'
 arch=('any')
 url='https://github.com/oznu/homebridge-config-ui-x'
diff --git a/homebridge-config-ui-x.install b/homebridge-config-ui-x.install
index b8f444a88110..286ce972650f 100644
--- a/homebridge-config-ui-x.install
+++ b/homebridge-config-ui-x.install
@@ -11,7 +11,7 @@ post_install() {
 	also modify /etc/sudoers. It is also capable of installing an
 	alternative binary of Node.js. It is recommended to *never* use it.
 
-	2) Installing or upgrading plugins from the web ui invokes `npm install`
+	2) Installing or upgrading plugins from the web ui invokes npm install
 	globally (/usr/lib/node_modules). You can alternatively package plugins as AUR
 	packages. Sticking with verified plugins can also provide a higher level of
 	security.
@@ -26,7 +26,7 @@ post_install() {
 	You have been warned. (@bret: Still true?)
 
 	5) It is recommended to run homebridge with a supported Node.js version.
-	Currently `nodejs-lts-iron` (Node.js 20) is the recommended version.
+	Currently nodejs-lts-iron (Node.js 20) is the recommended version.
 
 	6) To use systemd-resolved as the mDNS resolver, set up systemd-resolved mDNS
 	and then follow these instructions: