Writing and Editing: Word Choice and Word Order vs Technical Writing: How to Write Software Documentation

The course is dense with genuinely useful, sentence-level technique — deleting weak words, sharpening verbs, ordering clauses for emphasis — illustrated with sharp examples drawn from law, literature and rhetoric. Learners consistently call the material rich and eye-opening. The recurring caveat is volume: several reviewers say there is simply a lot to absorb, and that the density can make the structure feel cluttered if you are working through it quickly.

Patrick Barry, a law professor and director of digital academic initiatives at Michigan Law, is the strongest asset of the course. Reviewers describe him as knowledgeable, down-to-earth, funny and engaging, and his enthusiasm for the craft of editing comes through clearly. Almost no criticism is aimed at his teaching; the complaints are about format and pacing, not delivery.

Free to audit with full access to the video lessons, and a Coursera subscription only adds the peer-graded assignments and certificate. For a university course of this calibre, learners overwhelmingly rate value as excellent. The one reservation is that the graded practice — arguably where editing skill is cemented — sits behind the paywall.

The skills transfer directly to professional, legal and academic writing — anywhere precise, persuasive prose matters. Multiple reviewers, including experienced lawyers, report immediately tightening their own writing. The examples lean toward law and rhetoric, which is a strength for professional writers but means some illustrations feel less relevant to other fields.

The editing exercises are practical and directly tied to the lessons, which learners appreciate. The weak points are the same two that recur across Coursera writing courses: peer-reviewed grading can be inconsistent, and a minority found the assignment structure confusing relative to the volume of content being covered.

The course is structured across twelve thematic modules that map the complete technical writing lifecycle: foundational writing principles, documentation in software development teams, GitHub Wiki with Markdown, style guide construction, structured writing theory, the twelve principles of technical communication, DITA XML authoring inside Oxygen Author, visual communication with Canva and Google Slides, user research via card sorting in Mural, metadata and taxonomy for findability, information architecture strategies, and the technical writer's role within agile development workflows. Learners consistently describe the curriculum as "perfectly structured" and "immediately applicable" — two themes that surface across the vast majority of positive reviews. Karina Delcheva, a career-switcher who used the course to land her first technical writing role, noted that exercises with "easy-to-follow instructions and examples" were the deciding factor in her preparedness. Grace Tan echoed this by crediting the course with orienting her to "the standard and best practices in technical writing as well as the common tools that are used nowadays." The primary content limitation is currency: the course was last updated in February 2021. While foundational writing principles age slowly, tool-specific walkthroughs — particularly the Oxygen Author DITA XML demonstrations and Mural user research sections — reference interface versions that have since changed. Learners who prioritise learning the principles and adapt independently to updated tool UIs will find the content holds up; those expecting step-by-step current tool walkthroughs may encounter friction in a small number of modules.

Jordan Stanchev is a User Assistance Development Architect with eighteen-plus years in technical communications. He began his career as a Java developer before transitioning to information architecture, a dual background that gives him rare credibility when teaching the intersection of software development culture and documentation practice. He currently leads DITA XML-based infrastructure projects at a Fortune 500 company, which means the course is grounded in lived enterprise-scale documentation work rather than theoretical instruction. Reviewers across the JPDocu School's catalogue of ten courses (collectively serving 40,000+ students) consistently praise Stanchev's ability to demystify intimidating tools and workflows. His slides are described as "clear and simple" without being reductive. The course has been adopted as a teaching resource in European university curricula and used for onboarding new technical writers at multiple large organisations — third-party validation of the instructor's authority. The critique that surfaces most often is the absence of live Q&A or direct instructor feedback. Given the course's one-time purchase model and asynchronous delivery, learners who want mentorship during exercises must rely on the Udemy Q&A forum rather than direct coaching. For a course explicitly designed to prepare people for their first technical writing job, this gap is noticeable — peer discussion threads do not fully substitute for expert editorial review.

At approximately $17.99 (standard Udemy promotional pricing), the course offers an exceptional content-to-cost ratio. Nearly ten hours of on-demand video, nine articles, and fourteen downloadable resources — including style guide templates, DITA topic samples, and portfolio exercise assets — represent substantial material for a career-oriented curriculum in this price bracket. The downloadable resources are a particular differentiator: learners leave the course with portfolio-ready documentation samples and reusable templates, which IIM Skills and ClickHelp both highlight as key reasons to prefer this course over cheaper alternatives that provide only passive video content. For a learner whose goal is to secure a first technical writing role, the ability to demonstrate real documentation artefacts is worth considerably more than the course price in interview preparation value. The course is not free to audit — unlike some Coursera alternatives — but its one-time purchase model means no ongoing subscription. For learners who want the Coursera-style free option, the framing shifts: this course's value is in its practical deliverables, not in passive content consumption, which makes the audit-versus-purchase question less relevant.

The course's defining strength is its explicit career-transition orientation. Rather than teaching writing in the abstract, every module is framed around the tools, workflows, and expectations a technical writer encounters in a software development team. The GitHub Wiki with Markdown module alone equips learners with a skill required in nearly every entry-level technical writing job posting. The DITA XML module — while steep for beginners — introduces the structured authoring standard used in enterprise documentation at scale. The card sorting user research module, taught using Mural, is unusual in technical writing curricula and gives learners an edge when applying to companies that practice information architecture methodologies. Portfolio building is woven throughout: every major module includes a practical exercise designed to produce a documentation artefact that can be shared in a job application. One reviewer on Medium noted that the course "helped me understand more about software documentation as a relationship with all the parts involved in software development" — capturing the course's real differentiator: it teaches documentation as a systems problem, not merely a writing problem. This framing is far more useful in a professional context than courses that focus exclusively on grammar and style.