I have a JavaScript-based GraphQL API whose mutation section reads a bit flat. The structure and code samples are already in place; what’s missing is crisp, engaging language that tells developers exactly why, when, and how to use each mutation. Your task is to rewrite and refine the existing descriptions and explanatory paragraphs so they are consistent, technically precise, and easy to skim. You will work directly in the Markdown files stored in our Git repository. Please preserve every field, argument, type, and example exactly as implemented—only the surrounding prose should change. No need to add new code samples or error-handling notes; stay focused on elevating the narrative around each mutation. Deliverable: • Updated Markdown files for every mutation, with concise yet thorough descriptions and clear step-by-step explanations of inputs, return values, and typical use cases. Acceptance criteria: • All mutations documented in the repo include an improved description of purpose, parameters, and results. • Tone is developer-friendly, active voice, and free of jargon or ambiguous phrasing. • No schema details, code snippets, or formatting are altered outside the rewritten prose. If you live and breathe GraphQL and enjoy polishing technical writing until it shines, I’d love your help.