Update documentation for improved semantic clarity: Replace <Tip> with <Info> in multiple sections to enhance consistency and understanding of the content, while refining component usage guidelines in the contributing document.

Author: efraespada

CONTRIBUTING.md

@@ -63,7 +63,7 @@ npm run build
 - Update the relevant docs in `docs/` when changing behavior or adding features.
 - For user-facing changes, update `README.md` and the docs at [docs.page/vypdev/copilot](https://docs.page/vypdev/copilot).
 - The project uses [docs.page](https://docs.page/) (invertase) for publishing; see `docs.json` for sidebar structure.
-- Use only **docs.page components** so the site builds without errors: **Card**, **CardGroup** (for multiple cards in a row; use `cols={2}` or `cols={3}`), **Callouts** (e.g. Info, Warning, Tip), **Tabs**, **Accordion**, **Steps**, **Code Group**, etc. Do **not** use Mintlify-only components such as **Columns** (use **CardGroup** instead). See [docs.page Components](https://use.docs.page/components).
+- Use only **docs.page components** so the site builds without errors: **Card**, **CardGroup** (for multiple cards in a row; use `cols={2}` or `cols={3}`), **Callouts** (**Info**, **Warning**, **Error**, **Success** only — do not use Note or Tip), **Tabs**, **Accordion**, **Steps**, **Code Group**, etc. Do **not** use Mintlify-only components such as **Columns** (use **CardGroup** instead). See [docs.page Components](https://use.docs.page/components).
 
 ## Submitting Changes
 

docs/features.mdx

@@ -109,9 +109,9 @@ Configuration: `opencode-server-url`, `opencode-model`, and optionally `opencode
 
 ## Workflow concurrency and sequential execution
 
-<Tip>
+<Info>
   **Sequential runs:** When a new run starts, the action **waits** for any previous run of the **same workflow name** to finish. Runs of the same workflow (e.g. "Copilot - Issue") execute one after another instead of in parallel or being cancelled — something GitHub does not offer natively.
-</Tip>
+</Info>
 
 GitHub's native [concurrency](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#concurrency) lets you cancel in-progress runs when a new one starts (`cancel-in-progress: true`). Copilot adds **sequential execution** for the same workflow: when a new run starts, the action waits for any previous run of the same workflow name to finish before doing its work.
 

docs/pull-requests/ai-description.mdx

@@ -27,9 +27,9 @@ The AI is instructed to use your repository's **pull request template** as the s
 
 If you don't have a template, the agent will still produce a structured description, but defining a template ensures consistent, professional PR descriptions that match your team's expectations (e.g. Summary, Related Issues, Scope of Changes, Technical Details, How to Test, Breaking Changes, Deployment Notes, etc.).
 
-<Tip>
+<Info>
   **Recommendation:** Add a `.github/pull_request_template.md` in your repo with the sections you want (summary, scope, testing, breaking changes, etc.). The AI will use it as a guide and fill it with the information from the issue and the branch diff.
-</Tip>
+</Info>
 
 ## When the AI description runs
 

docs/testing-opencode-plan-locally.mdx

@@ -77,9 +77,9 @@ node build/cli/index.js recommend-steps -i <issue-number> -t <PAT>
 
 ## 4. Optional: .env File
 
-<Tip>
+<Info>
   You can store your token and OpenCode settings in a `.env` file so you don't need to pass `-t` and OpenCode options every time.
-</Tip>
+</Info>
 
 Create a `.env` file in the repo root (do **not** commit it):