docs: clarify that custom compose command replaces the default instead of appending

The docs claimed the Command field appends to the default command, but
createCommand in dokploy fully replaces it with the custom command.
Update both pages to describe the override behavior.

Fixes #142

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

apps/docs/content/docs/core/docker-compose/index.mdx

@@ -65,7 +65,7 @@ We provide a webhook so that you can trigger your own deployments by pushing to
 
 This section provides advanced configuration options for experienced users. It includes tools for custom commands within the container and volumes.
 
-- **Command**: Dokploy has a defined command to run the Docker Compose file, ensuring complete control through the UI. However, you can append flags or options to the command.
+- **Command**: Dokploy has a defined command to run the Docker Compose file, ensuring complete control through the UI. However, you can override it with a custom command. Note that the custom command fully replaces the default one (it does not append to it), so if you only need extra flags like `--force-recreate`, you must write the full command based on the default shown in the UI. The command always starts with `docker`, so a custom command like `compose -p <app-name> -f <compose-path> up -d --build --remove-orphans --force-recreate` will run as `docker compose ...`.
   
   <Callout type="info" title="Using Private Registries with Docker Stack">
   If you're deploying with **Docker Stack** (Docker Swarm mode) using **replicas** and a **private registry**, you need to add the `--with-registry-auth` flag to ensure that registry credentials are properly distributed to all nodes in your swarm.

apps/docs/content/docs/core/features.mdx

@@ -72,7 +72,7 @@ Enhance your Docker Compose experience with these advanced functionalities:
   2. Cancel queued deployments in case you have a lot of deployments in the queue, the most common is when you push alot of times in your repository, you can cancel the incoming queues, not the deployments that are already running.
 
 **Advanced Settings**:
-  1. Append command, by default we use a internal command to build the docker compose however, you can append a command to the existing one.
+  1. Custom command, by default we use an internal command to build the docker compose, however you can override it with your own command. Note that the custom command fully replaces the default one (the default command is shown in the UI as a reference, and the command always starts with `docker`).
   2. Manage volumes and mounts.
 
 ## Database Deployment