docs: smooth "engineers can then type" phrasing in README and guide

Swap the mechanical role-subject narration ("Engineers can then type /
Engineers then type...") for a cause-effect construction ("Once
published, `vp create @org` opens..."). Reads naturally and drops the
implicit assumption that every reader identifies as an "engineer".

Author: fengmk2

docs/guide/create.md

@@ -89,7 +89,7 @@ vp create https://github.com/user/template-repo
 
 ## Organization Templates
 
-An organization can publish a curated set of templates under a single npm scope by shipping an `@org/create` package whose `package.json` carries a `vp.templates` manifest. Engineers then type the scope and get an interactive picker over the listed templates.
+An organization can publish a curated set of templates under a single npm scope by shipping an `@org/create` package whose `package.json` carries a `vp.templates` manifest. Once published, `vp create @org` opens an interactive picker over those templates.
 
 ### Pick from an org
 

packages/cli/README.md

@@ -152,9 +152,9 @@ You can run `vp create` inside of a project to add new apps or libraries to your
 
 Organizations can expose a curated set of templates under their npm scope by
 publishing `@org/create` with a `vp.templates` manifest in its `package.json`.
-Engineers can then type `vp create @org` to pick from that list
-interactively, or set `create: { defaultTemplate: '@org' }` in
-`vite.config.ts` to make it the default for bare `vp create`. See the
+Once published, `vp create @org` opens an interactive picker over those
+templates, and setting `create: { defaultTemplate: '@org' }` in
+`vite.config.ts` makes it the default for bare `vp create`. See the
 [Organization Templates guide](https://viteplus.dev/guide/create#organization-templates)
 for the authoring workflow and
 [`create.defaultTemplate`](https://viteplus.dev/config/create) for the