Write microcopy for one flow's buttons, empty states, and confirmations as a single consistent voice

Write the microcopy for every touchpoint in the flow below at once, as one voice pass — buttons, empty states, confirmation messages, and tooltips. Microcopy is usually written string-by-string as each screen gets built, which is exactly how a product ends up with three different tones and two different ways of saying "delete" across one flow; writing it all together is how that gets caught.

FLOW AND EVERY STRING NEEDED
A shared-document flow: 'Share' button, empty state for a document with no collaborators yet, confirmation for removing a collaborator, tooltip on the 'view-only' permission toggle.

BRAND VOICE REFERENCE
Warm and plainspoken, avoids corporate jargon, occasional light humor in low-stakes moments, never uses exclamation points in more than one string per screen.

USER'S EMOTIONAL STATE AT KEY MOMENTS
Slight anxiety when removing a collaborator (worried about hurting the relationship or losing shared work); mild uncertainty at the empty state (not sure if sharing is even worth setting up yet).

RULES
Write every string in the same voice, established by the brand voice reference — but adapt tone within that voice to the emotional context at each moment; the voice stays consistent (word choice, formality, use of humor or restraint) while tone shifts appropriately (a delete-confirmation for a destructive action should not carry the same playful tone as an empty-state illustration caption, even in an otherwise playful brand voice). For every destructive or hard-to-undo action, the confirmation copy must state specifically what will happen and whether it can be undone — never a bare "Are you sure?" with no information added. For every empty state, the copy must tell the user what to do next to fill it, not just describe the absence ("No items yet" alone is a description; "Add your first item to get started" is actionable). Check every string against every other string in the set for consistency of terminology — if one button says "Remove" and another says "Delete" for functionally the same action, flag it and pick one term to use throughout. Keep every string as short as it can be while still being specific — cut filler words, but never cut the specific information (what will happen, whether it's reversible) needed for a confirmation to actually inform a decision.

WHAT NOT TO DO
Do not write generic placeholder-style copy ("Click here") that a template would produce regardless of context. Do not use exclamation points or forced enthusiasm on error or destructive-action copy even if the brand voice is generally upbeat elsewhere.

OUTPUT FORMAT
A table: Location in flow | String | Purpose (button / empty state / confirmation / tooltip). Follow with a short 'consistency check' note listing any terminology conflicts you found and resolved across the set.