fix: clarify cpu_shares comment in compose.yaml

Agent-Logs-Url: https://github.com/nextcloud/all-in-one/sessions/fb6684cd-3659-4b09-9cca-72d1c42e736c

Co-authored-by: szaimen <42591237+szaimen@users.noreply.github.com>

compose.yaml

@@ -4,7 +4,7 @@ services:
     image: ghcr.io/nextcloud-releases/all-in-one:latest # This is the container image used. You can switch to ghcr.io/nextcloud-releases/all-in-one:beta if you want to help testing new releases. See https://github.com/nextcloud/all-in-one#how-to-switch-the-channel
     init: true # This setting makes sure that signals from main process inside the container are correctly forwarded to children. See https://docs.docker.com/reference/compose-file/services/#init
     restart: always # This makes sure that the container starts always together with the host OS. See https://docs.docker.com/reference/compose-file/services/#restart
-    cpu_shares: 1024 # This setting ensures the mastercontainer gets a higher CPU share compared to other containers for better responsiveness under heavy load. See https://docs.docker.com/reference/compose-file/services/#cpu_shares
+    cpu_shares: 1024 # This explicitly sets the CPU share weighting (default is 1024). Increase this value (e.g. to 2048) to give the mastercontainer higher CPU priority over other containers for better responsiveness under heavy load. See https://docs.docker.com/reference/compose-file/services/#cpu_shares
     container_name: nextcloud-aio-mastercontainer # This line is not allowed to be changed as otherwise AIO will not work correctly
     volumes:
       - nextcloud_aio_mastercontainer:/mnt/docker-aio-config # This line is not allowed to be changed as otherwise the built-in backup solution will not work