docs: Fix important note

README.md

@@ -171,8 +171,10 @@ For more information on why this is the case, refer to the following article:
 However, you can circumvent this limitation by dividing your workflow into two separate workflows (see examples below):
 
 1. **Testing Workflow**: This workflow runs tests in response to the `pull_request` trigger, within the context of the actual pull request, and uploads the coverage reports as artifacts.
+
     > [!IMPORTANT]
     > This workflow must reside within your default branch (`main`)!
+
 2. **Reporting Workflow**: This workflow is triggered upon the completion of the **Testing Workflow** using the `workflow_runs` event. It downloads and parses the coverage report, and posts a comment on the pull request.
 
 This action will automatically detect: