Apply suggestion from @camilamacedo86

Co-authored-by: Camila Macedo <7708031+camilamacedo86@users.noreply.github.com>

Author: vitorfloriano

docs/book/src/reference/commands/alpha_update.md

@@ -111,27 +111,23 @@ These conflicts will be committed in the
 <aside class="note warning">
 You must manually resolve these conflicts before merging into your main branch.
 
-### Required Steps If Conflicts Are Present
+```suggestion
+<aside class="note warning">
+<H1>If you face conflicts (using or not the --force flag) </H1>
+If the merge introduces conflicts, you must resolve them and **ensure** you execute the following command to regenerate the manifests and organise the files properly:
 
-If the merge introduces conflicts, follow these steps before committing any final changes:
-1. Resolve Conflicts;
-2. Open the conflicted files and manually edit them to resolve all merge markers;
-3. Run Required Make Targets;
-4. After resolving, run the following command to regenerate, format, vet, and lint the code:
-```
+```bash
 make manifests generate fmt vet lint-fix
 ```
 
-### Optional (but Recommended)
+Alternatively, you may want to run:
 
-1. Run the full validation suite to ensure your project remains consistent and working:
-```
+```bash
 make all
 ```
-2. Create Pull Request
- After validation, commit your changes and push a pull request from `tmp-kb-update-merge` to your target branch.
 </aside>
 
+
 ## When to Use `--force`
 Use `--force` only in scenarios like:
 - Automated environments (e.g., CI pipelines or cron jobs)