redpin pass

Author: bdenham

src/content/docs/merchants/quick-start/content-model.mdx

@@ -18,20 +18,20 @@ Splitting styling from content this way keeps site design consistent.
 
 ## How the roles work together
 
-A layout option must exist before a Content Author can pick it. But that doesn't mean the two roles always work one after the other. A Page Designer can build new layout options directly in the storefront's code while a Content Author picks from options that already exist and builds pages without touching code.
+A layout option must exist before a Content Author can pick it. However, the two roles do not always work sequentially. A Page Designer can build new layout options directly in the storefront's code while a Content Author picks from options that already exist and builds pages without modifying code.
 
 A hero banner, for example, might offer a two-column layout and a full-width layout, each built and tested ahead of time.
 
 {/* TODO: replace with a concrete, publishable example of a variation set (for example, a hero banner). Pending: access to genericized OPTP/eLuscious walkthroughs (blocked on clearance for public use), or an example built from this boilerplate's own blocks/section metadata instead. */}
 
-When a Content Author needs a layout option that doesn't exist yet, or an entirely new kind of block, the request goes to the Page Designer. If that need is a new drop-in, live catalog data, or a change to existing behavior, it becomes a developer task instead — the drop-in work outside a Page Designer's scope. See [Author and developer tasks](/merchants/blocks/author-and-developer-tasks/) for how to file that request.
+When a Content Author needs a layout option that doesn't exist yet, or an entirely new kind of block, the request goes to the Page Designer. If that need is a new drop-in, live catalog data, or a change to existing behavior, it becomes a developer task outside the Page Designer's scope. See [Author and developer tasks](/merchants/blocks/author-and-developer-tasks/) for how to file that request.
 
 ## Templates for content pages
 
-Page Designers create templates for common content pages, such as a landing page or a category page, so Content Authors can start from the right baseline instead of an empty page. A Content Author selects the template that most closely matches their needs and builds from there.
+Page Designers create templates for common content pages, such as a landing page or a category page, so Content Authors can start from the right baseline instead of starting from an empty page. A Content Author selects the template that most closely matches their needs and builds from there.
 
 ## Reference implementations
 
 Reference implementations for this page are coming soon.
 
-{/* TODO: add reference implementation examples built from this boilerplate's own blocks and section metadata. OPTP/eLuscious access was declined for public use (Oleg Posyniak, Slack, 2026-08); this page stays in the Commerce storefront docs, not Experience League, per the same thread. */}
+{/* TODO: add reference implementation examples built from this boilerplate's own blocks and section metadata. Access was restricted for public use (Oleg Posyniak, Slack, 2026-08); this page stays in the Commerce storefront docs, not Adobe Experience League, per the same thread. */}