Merge remote-tracking branch 'origin/docs/cleanup-4.8'

docs/upgrade/faq-issues.adoc

@@ -14,15 +14,15 @@ NOTE: Always upgrade to the latest midPoint 4.4-based release before attempting
 Evolveum has created xref:/midpoint/methodology/first-steps/[First Steps Methodology] to guide your midPoint deployment.
 Even if you are upgrading from midPoint 4.4 LTS and not installing from scratch, some of the information may be valuable for you as the methodology explains the new midPoint deployment approach leveraging xref:/midpoint/reference/admin-gui/simulations/[simulations] and other midPoint 4.8 features.
 
-=== midPoint attempts to start the old (4.4-based) midPoint version instead of the new one when using Systemd
+=== midPoint attempts to start the old (4.4-based) midPoint version instead of the new one when using Systemd or service startup scripts
 
-*Make sure you have updated your Systemd service unit file for midPoint.*
+*Make sure you have updated your Systemd service unit file / service startup script for midPoint.*
 
 midPoint 4.4 uses `midpoint.war` while new midPoint 4.8 uses `midpoint.jar` file!
 
 If you have followed xref:/midpoint/reference/deployment/ninja/upgrade-with-ninja/[Upgrade with Ninja] page, after the application is upgraded, the `lib/` directory contains both (old) `midpoint.war` and (new) `midpoint.jar`.
 
-Please fix your Systemd service unit file for midPoint.
+Please check and fix your Systemd service unit file or service startup file for `midPoint.war` references and replace them with `midpoint.jar`.
 
 See also xref:/midpoint/install/systemd/[Running midPoint with systemd].