README: name the per-source conversions, not just the tools

The tools were listed — Lovable, Bolt, v0 — but never in the form anyone
searches for them, and the heading said "Convert a Lovable project" without
saying to what. One sentence where the input table already sits, and the
heading finished, both making the same point the page needs to make anyway:
there is no per-tool importer. By the time it converts them they are the same
folder of HTML.

Author: BELNEM s.r.o

README.md

@@ -176,7 +176,7 @@ Installed this way it is a plain skill rather than a plugin skill, so it is
 invoked directly by name (or `/html2wp` in Claude Code).
 </details>
 
-## Convert a Lovable project
+## Convert a Lovable project to WordPress
 
 **If you have a licence key, set it up first** — once per machine, from any
 directory. On the free tier skip this and change nothing else:
@@ -234,6 +234,10 @@ say where — a path is a complete answer:
 convert ./dist
 ```
 
+Lovable to WordPress, Bolt to WordPress, v0 to WordPress, a design made in
+Claude — one pipeline, and there is no per-tool importer: by the time it
+converts them they are all a folder of HTML, CSS and assets.
+
 | What you have | What to say |
 |---|---|
 | a project that builds to a site — Lovable, Bolt, v0, Vite, Astro, Next export | `convert this project` |