Can You Self Publish Without An Editor

Gary Smailes | 29 December 2025

What “Publishing Without an Editor” Actually Means

Publishing without an editor means you take on the roles an editing team would cover. Not once, but in stages. Each stage fixes a different problem, and skipping one leaves a gap somewhere readers will feel, even if they cannot name it.

The four editing jobs

• Developmental editing. Big picture. Structure, story logic, character arcs, scene order. Example: Chapter 7 repeats the same argument as Chapter 4. The clue in Chapter 12 has no setup. The midpoint has no turn. A developmental pass reshapes, cuts, or adds scenes so momentum holds and payoffs land.
• Line editing. Sentence level. Voice, rhythm, meaning. You trim flab, sharpen verbs, and choose images that fit the tone. Example: “She walked quickly across the room” becomes “She hurried across the room.” “He felt angry” becomes “Heat rose in his neck.” You keep the voice true and the reading smooth.
• Copyediting. Mechanics and consistency. Grammar, punctuation, usage, and style. Example: You pick email or e-mail and stick with it. You decide on U.S. spelling or U.K. spelling and stay consistent. You fix subject-verb agreement, stray commas, and timeline slips.
• Proofreading. Final eyes before release. Typos, missing words, spacing, headers, page breaks, table of contents, links. The book looks finished, not rushed.

Each job serves a different reader need. Story. Clarity. Trust. Clean pages.

What changes when you self publish

In traditional houses, a team funds several rounds. A dev editor sends big notes. A line editor refines voice. A copyeditor polishes. A proofreader catches last errors before print and digital conversion.

In self-publishing, you manage the process. You decide which steps to pay for, and which to replace with your own labor and community help. Think like a producer. Sequence the work. Set deadlines. Track decisions.

Some authors hire a single pass and fill the gaps with beta readers and tools. Others pay for a high-level editorial letter, then do the heavy lifting themselves. There is no one path, only trade-offs you choose with eyes open.

Why blind spots grow without an editor

Familiarity hides problems. You know what a scene means, so your brain supplies missing parts. A stranger will not do that.

• Plot holes. You cut a setup during a late-night trim, then the reveal makes no sense. You read right past the gap because you remember the old draft.
• Continuity. Hair is shoulder-length in Chapter 3, a pixie in Chapter 4, no salon in between. A side character is Tom for fifty pages, then turns into Tim.
• Clunky dialogue. “As you know, sister, we grew up in Omaha” slides by because you are eager to land the backstory. A reader hears a lecture.
• Style drift. Double quotes switch to single halfway through. Numbers bounce between words and digits. You alternate between healthcare and health care.

A good editor flags these on sight. Without one, you build systems to catch them.

Actionable: a 3 chapter audit

Start small. Test the book’s health in the first three chapters. If the opening is tight, the rest tends to follow. If it wobbles, you know where to focus.

Set up

• Rest the draft for a week. Print the three chapters or load them on an e-reader. Turn off track changes for this pass.
• Keep a notepad with three columns: Structure, Style, Mechanics.

Structure check

• For each chapter, write a one-line summary. Goal, obstacle, outcome. If you cannot state a turn, the scene likely sags.
• Mark repeated beats. Two arguments that do the same job. Two scenes that deliver the same clue.
• List promises made. A gun on the mantel, a vow, a deadline. Note where the book follows through.

Style check

• Read aloud. Circle any line that trips your tongue.
• Highlight filter phrases. She saw, he noticed, I realized. Replace where possible with direct observation.
• Strike throat clearing. Hellos, goodbyes, weather reports, walking through doors. Start where the heat starts.
• Tag character voices. Pick one sentence per character that shows unique vocabulary or rhythm. If you struggle, the voices blend.

Mechanics check

• Mark any spelling you hesitate over. Add it to a style sheet.
• Note punctuation patterns you favor. Long strings of commas. Overuse of exclamation points. Plan to reduce noise.
• Track names, ages, distances, dates, and time of day. Build a timeline if you feel a wobble.

Decision

• Choose the biggest gap by column. Structural, stylistic, or mechanical. That choice sets your next pass.
• Schedule one focused pass for that gap across the full book. Do not multitask. Depth wins.

Build a style sheet before any DIY pass

A style sheet keeps your decisions consistent. Editors use them. You should too. Create a simple document and keep it open during every pass.

Basics

• Spelling preference. U.S. vs U.K. color/colour. Program/programme.
• Hyphenation. email or e-mail. Health care or healthcare. World building or worldbuilding.
• Capitalization. Internet or internet. Department names. Honorifics.
• Numbers. One to nine spelled out, 10 and above as digits, or your chosen rule.
• Dates and time. 5 p.m. or 5 PM. Day-month-year or month-day-year.
• Dialogue style. Double quotes for speech, single quotes for quotes within speech.
• Italics. Thoughts, foreign words, ship names. Define where you use italics and where you do not.

Story bible

• Character list. Full names, nicknames, pronouns, physical notes, jobs, quirks. Ages by chapter.
• Places. Street names, towns, spellings, landmarks.
• Timeline. Key dates, holidays, school terms, moon phases if relevant.
• Recurring terms. Magic system nouns, tech jargon, ranks. Chosen capitalization.

Example entries

• Spelling: email, Wi‑Fi, OK, toward, judgment.
• Numbers: spell out one through nine, use digits for dates, ages, and measurements.
• Dialogue: “ ” for speech. ‘ ’ for nested quotes. Emphasis with italics, not ALL CAPS.
• Names: Katherine “Kat” Li. Uses Kat in dialogue. Katherine on legal documents.
• Timeline: Day 1, Monday, Sept 14. Car breaks down in Chapter 2. Chapter 3 occurs the same night.

Keep it short, but keep it live. Every time you answer a question in the margins, add the answer to the sheet. When you hand the book to a proofreader later, the sheet saves them hours. When you revise a sequel, the sheet saves you from tripping over your own lore.

A quick test to finish

Pick one page in Chapter 1. Read it aloud once at normal speed. Now whisper it. If the rhythm still holds and no line feels bulky, your line work is close. If you stumble on the same words twice, flag them. Then add the trouble words to a personal watch list on your style sheet.

Publishing without an editor is a choice about labor, money, and risk. Treat those four jobs as separate, build a light system around them, and your book steps into the world with a stronger spine. Readers feel the difference on page one.

Risks and Trade-Offs for Indie Authors

Readers buy stories, then judge delivery. Editing shapes delivery. Weak pages drain trust fast. Sales follow trust.

Reader expectations drive sales

On Amazon KDP and other stores, reader behavior drives visibility. Low star averages reduce clicks. Refunds grow. Fewer clicks and shorter sessions signal trouble, which pushes a book out of recommendation loops. A 3.2 average sits cold. A 4.3 average earns second chances from browsers.

A quick gut check

• Open your book’s first ten pages. Mark one reason a stranger would stop reading on each page. Slow start. Confusing sentence. Typo. Fix those first.
• Compare your product page with the top five books in your subgenre. Cover, description, Look Inside. If tension drops during the sample, shoppers back out.

Genre magnifies risk

Genres come with contracts. Break the contract, readers walk.

• Mystery and thriller. Clues must line up. Red herrings must feel fair. One missing setup ruins the reveal. Readers talk, and they love logic.
• Romance. Dialogue needs heat and respect. Emotional beats drive payoff. If a black moment feels pasted on, reviews call it out. Consent language and intimacy details matter.
• Science fiction and fantasy. World rules need consistency. Magic limits, tech constraints, maps, calendars. A moon phase out of order, a rank used wrong, a teleporter with new rules in chapter twenty, readers spot every wobble.
• Historical. Dates, attire, idiom. A zipper where no zipper existed draws focus away from the scene.
• Nonfiction. Claims need sources. Numbers need accuracy. One wrong stat poisons authority.

Genre readers are generous with passion, not with errors.

Skipping pro help often costs more later

Repair work comes with fees you did not plan for. New files. Fresh ISBNs in some cases. Reformatting for print and EPUB. Re-uploading across vendors. Ads paused and restarted. A cover refresh to signal a cleaner edition.

Time adds up. Momentum fades. A name gathers mixed reviews which follow every future release. A relaunch helps, but ad spend climbs when trust drops.

A quick story. An indie thriller launched with a 3.5 average after twenty reviews. The author pulled back, hired an editorial assessment, fixed clue logic, and cleaned dialogue. Three months later, a v1.1 upload went live with a new subtitle. New reviews landed at 4 and 5 stars. Ad cost per sale still ran higher than peers for two months while old reviews sat on page one. Recovery worked, but the tab included time, cash, and lost ranking.

Offset the risk if you skip pro editing

You can raise quality without a full editorial package. Work smarter, plan for feedback, watch the signals.

• Extend beta cycles. Recruit genre-savvy readers. Use a question sheet, not a blank page. Examples. Where did attention dip. Which scene felt false. Any confusion about timeline. Any deal-breaker moments. Treat notes like data. Look for patterns across readers.
• Run a soft launch. Start with your mailing list and a small ARC team. Delay wide ads. Give the sample to readers who buy fast. Watch early comments and support emails for quality flags.
• Cap ad spend until organic reviews confirm quality. Set a review target before scaling. For many niches, ten to twenty reviews with a stable average above 4.2 signals readiness. Adjust for your genre.
• Monitor returns and read-through. On KU, check page reads after day three. Sudden drop-offs near chapter openings often point to scene-level problems. High refund rates on sales point to quality gaps or mismatched description.
• Prepare a v1.1 plan. Keep a change log. Tag issues by type, structural, stylistic, mechanical. Batch fixes. When ready, upload new files, then tell your list a cleaner edition is live. Avoid arguing with reviewers. Show improvement by improving.
• Protect the next book. Track common errors from reviews and your log. Build a checklist on page breaks, punctuation tics, filler words, and continuity notes. Run that checklist before formatting.

A short pre-mortem exercise

Grab a timer and a pad. Five minutes per prompt.

• Write three lines a future one-star reviewer might post. Be blunt. “Typos on page one.” “Villain twist made no sense.” “Dialogue sounded like a lecture.” Now turn each line into a task.
• Read the top fifty reviews for three leaders in your subgenre. Note complaints which repeat. Add those to your task list.
• Draft a one-paragraph plan for a v1.1 update. Files, dates, helpers, mailing list note. A plan lowers stress when feedback stings.

The trade-off, stated plainly

Fast release without strong editing buys speed, not trust. Careful revision with reader testing buys trust, not speed. Choose based on goals for this project. Low-stakes serial, pen name experiment, hungry audience which forgives rough edges. Fine. A strong edit later might still be smart before a box set. Flagship novel, wide print dreams, library hopes. Delay, book help, and arrive with fewer fires.

Readers forgive only once or twice. Give them a clean read, or give them a clear reason to believe a cleaner read arrives soon.

A DIY Editing Workflow That Raises Quality

Quality grows from process, not luck. Use a clear path, one pass at a time, and the draft will sharpen.

Step 1: Take a rest period

One to two weeks away from the pages resets perspective. Distance turns guesswork into judgment.

Quick setup

• Rename the file with a date. Move the file to a “cooling” folder.
• Leave a one-line note to future you. Purpose, audience, promise.
• Read in your genre. Study first chapters and turning points. Take light notes, not a thesis.

Step 2: Build a reverse outline

Open a spreadsheet or a stack of index cards. One row or card per scene.

Track

• Location and time stamp.
• Point of view and cast.
• Purpose of the scene in one line.
• Goal, conflict, outcome.
• What changes by the end.

Now scan for problems

• Repeated beats or conversations.
• A middle stretch with no change.
• Missing setup for a later payoff.
• A timeline that drifts.

Mark fixes, not prose. Focus on structure first.

Step 3: Run a scene health check

Strong scenes move. Weak scenes sit.

For each scene, confirm four parts

• Goal. A clear want.
• Obstacle. A person, rule, or force in the way.
• Stakes. Loss or gain if success or failure lands.
• Turn. Outcome that shifts direction. “Yes, but” or “No, and.”

No turn, no scene. Trim or merge. Or raise pressure until a turn appears.

Mini drill

• Print three scenes. Highlight the moment of change in yellow.
• If no highlight appears, write a new beat that forces change.

Step 4: Do a line-level clarity pass

Switch to sentences. Keep meaning, lose fog.

Targets

• Hedges. Kind of, sort of, a bit. Strike or replace with a concrete detail.
• Empty intensifiers. So, super, totally. Replace with a stronger noun or verb.
• Filters. She felt, she saw, she noticed, he realized, he knew. Drop the filter and let the sensory detail stand.
• Weak verbs. Use a precise action. “He went across the room” becomes “He crossed the room.”
• Redundancy. Say things once. Trust readers to remember.

Two tools help here. A search for “ly” tags many adverbs. A read-aloud session exposes knots and filler.

Step 5: Polish dialogue

Great dialogue sounds like speech with the boring parts removed.

Tips

• Read scenes aloud with a timer. Stumbles flag clunky lines.
• Cut greetings, farewells, and small talk unless tension hides underneath.
• Give each character a distinct vocabulary and rhythm. One uses short snaps. Another favors long, winding questions. Keep a small voice note for each recurring character.
• Replace on-the-nose lines with subtext. Wants and fears leak through implication.

A quick test

• Cover names and dialogue tags. Can a stranger guess the speaker from word choice and sentence shape. If not, adjust voice cues.

Step 6: Copyedit with tools and a style sheet

Bring in mechanical support.

• Run Grammarly, ProWritingAid, or LanguageTool for grammar, punctuation, and spelling. Accept only clear wins. Flag edge cases for later review.
• Use PerfectIt for consistency. Hyphenation, numbers, abbreviations, terms.
• Choose a guide, such as CMOS. Record decisions on a style sheet.

Style sheet basics

• Spelling and hyphenation rules.
• Capitalization choices.
• Character names, ages, and unique terms.
• Timeline notes and holidays.
• Numbers, units, and dates.
• Dialogue punctuation rules and preferred dashes or ellipses.

Keep the sheet near the manuscript at all times. Update after every pass.

Step 7: Proof with text-to-speech

A voice catches what eyes skip. Load the text into a TTS tool. Listen with a pencil in hand.

Listen for

• Missing words or doubled words.
• Homophones. Bare versus bear, peak versus peek.
• Rhythm traps where sentences fight the tongue.
• Names or terms pronounced two ways, a clue to hidden inconsistency.

Pause and mark. Fix later to keep momentum.

Step 8: Format, then proof on real devices

Prepare files before the final proof. Different screens reveal different gremlins.

• Convert to EPUB and PDF in Vellum, Atticus, or Scrivener.
• Proof on an e-ink device, a phone, a tablet, and a printed proof.
• Look for widows and orphans, extra spaces, bad hyphenation, TOC hiccups, headers that break logic, and dead links.
• Check image placement and resolution.
• Review front and back matter. Series order, newsletter link, ISBN, and acknowledgments.

Mark errors on a checklist by page number or chapter number. Batch fixes to reduce re-exports.

Step 9: Schedule discrete passes

Work flows best in lanes. Avoid mixing structure with commas.

Suggested order

• Structure pass. Reverse outline and scene health.
• Line pass. Clarity and dialogue.
• Copy pass. Style sheet and tool runs.
• Format-proof pass. Device checks and print proof.

Use a tracker

• Log each pass with a date and scope.
• Add recurring problems to a “watch” list. Example entries. Overuse of stage directions. Timeline slips on weekdays. Repeated sentence openings.
• Fold watch items into the next draft plan.

A quick weekly plan

• Monday. Reverse outline updates for three chapters.
• Tuesday. Scene health checks for those chapters.
• Wednesday. Line pass on the same pages.
• Thursday. Tool pass and style sheet updates.
• Friday. Read-aloud or TTS for the week’s pages.
• End of month. Compile files and run a device proof.

This workflow trades rush for clarity. Follow the lanes, protect the style sheet, and the book will read cleaner, page by page.

Budget-Savvy Alternatives to Full Editing

Editing on a budget is possible. Spend where it moves the needle, replace the rest with smart systems.

Editorial assessment

An assessment gives you a high-level report on structure and market fit. No line edits, no commas, pure diagnosis.

What you receive

• A memo on hook, genre promise, stakes, character arcs, pacing, and timeline logic.
• Notes on comps, positioning, and first chapter performance.
• Clear next steps you implement yourself.

How to use it

• Before hiring, write a one-page synopsis and list three worries. Example worries. Slow middle. Weak antagonist. Series setup confusion.
• Ask for a report with page cites and a one-page summary.
• Turn the memo into a fix plan. Scene list, adds and cuts, order of operations.
• Revise, then run a short beta round to confirm the changes worked.

Ballpark cost ranges widely by length and experience. Think hundreds, not thousands, for many indie-friendly editors.

Mini exercise

• Draft a back-cover style hook in two sentences.
• Mark your midpoint scene. Write in one line what changes there.

Sample or partial edits

Hire a pro for the first 30 to 50 pages. Treat those pages as a model for voice and clarity across the book.

What to request

• Track Changes on sentences with margin notes saying why.
• A brief style note at the end. Patterns, pet words, point of view slips, tense drift.
• Two or three edited pages from the middle as a spot check.

How to leverage the sample

• Build a style sheet from the notes. Spelling, hyphenation, capitalization, dialogue punctuation, character terms.
• Apply the edits to the next three chapters on your own. Compare your pages to the sample to check alignment.
• Keep a list of repeated issues. Front-load fixes in your next pass.

Critique partners and beta readers

Genre-savvy readers will point to confusion and boredom faster than any tool.

Recruit

• Tap genre groups on Discord or Reddit, local writing circles, and newsletters where ARC swaps happen.
• Ask for readers who love your exact subgenre. Cozy mystery is not the same as hard-boiled.
• Share a clean PDF, a deadline, and a question sheet.

Give them a focused brief

• Where did your interest dip.
• Was the goal clear in each chapter.
• Did stakes feel high enough.
• Any lines you would highlight as great or cut as filler.
• Any spot where you flipped back to check who, where, or when.

Collect notes with a form. Look for patterns. One outlier is taste. Three readers pointing to the same lull means a fix.

Quick workflow

• Week 1. Send draft and questions.
• Week 2. Midpoint nudge and thank-you.
• Week 3. Collect, triage, revise.

Offer a small thank-you. Early copy, name in acknowledgments, a gift card if budget allows.

Sensitivity readers

If you write outside lived experience, hire readers with target expertise. They flag representation issues and reduce harm.

Where they help

• Cultural background, religion, language.
• Disability, neurodiversity, health.
• LGBTQIA+ identities.
• Professions with strict norms. Law, medicine, law enforcement, the military.

Process

• Share a focused brief. Role, age range, setting, and your intent.
• Ask for page numbers, examples, and alternative phrasing.
• Pay fair rates. Treat this as professional work, not volunteer labor.
• Revise with care, then ask for a quick recheck on changed pages.

Barter and community

Trade skills and pages. Indie authors do this every day.

Ideas

• Chapter swaps with clear scope. Two chapters each, margin notes only, seven-day turnaround.
• Proofreading trades between launch schedules.
• Newsletter swaps or a blurb in exchange for a scene-level read.
• Group buys with editors who offer installment plans or limited scopes.

Set terms upfront

• Word count, depth of feedback, deadline, format.
• One test chapter before expanding the swap.
• A simple shared style sheet to keep names and terms aligned.

Directories worth a look

• EFA and Reedsy list vetted editors. Many offer partials, payment plans, or assessments.

Staged spending

Spend in stages, in line with risk.

Priority order

1. Cover and metadata. Good design plus clean keywords and categories lifts visibility.
2. One targeted edit. Assessment, sample line edit, or a proofread. Choose based on your manuscript’s weakest link.
3. Final proof, even if everything else stayed DIY. Fresh eyes in the last mile stop typos from tanking reviews.

Pick based on genre risk

• Mystery or thriller. Pay for logic review or a clue map check.
• Romance. Invest in a dialogue and emotional beat tune-up for opening chapters.
• SFF. Ask for a continuity pass on timelines, terms, and world rules.

A quick budget plan you can use today

• Cap your spend at a number you can live with after rent and food. Write it down.
• Pick the highest ROI move for your biggest risk area. One only.
• Time the paid slot before formatting. Leave a buffer for fixes.

Worksheet

• My top risk area is __________.
• One paid intervention to address it is __________.
• Three no-cost supports I will use are __________. Example. Beta readers, a scene checklist, and a TTS proof.
• Date to book the pro __________. Date to send files __________. Date to implement changes __________.

Smart editing is triage. Spend where it saves the book. Replace the rest with process and community. Keep the receipts, keep your style sheet close, and publish with a clear head.

Readiness Checklist and Decision Framework

You want to know if the book is ready. Use this checklist. No vibes, no wishful thinking. Pass the tests or postpone.

Quality checks: pass or postpone

• Reverse outline updated. Scenes listed, goals clear, setups pay off.
• Two full read-aloud passes. Mouth on every word.
• TTS proof from start to finish. Listen for missing words, duplicates, and clunks.
• Style sheet finalized. Spellings, hyphenation, capitalization, names, places, timeline.
• Zero known typos in the final proof. Not “close.” Zero.

How to pressure test yourself

• Print the first 30 pages. Read with a ruler. Mark any stumble. Fix before moving on.
• Run a fresh spell-check after locking the style sheet. Add house spellings to the dictionary.
• Open the EPUB on your phone. Scroll like a shopper. Stop at the first snag, then fix it at the source file.

Pass all five, proceed. Miss one, you are not ready.

External validation: readers before retailers

• Notes from 3 to 5 genre-savvy beta readers. Not friends who love you, readers who love the category.
• Key issues addressed. No open threads from the feedback list.
• Look Inside pages tested for grip. The first 10 pages hold attention without coaching.

Give readers a tight brief

• Where did your interest dip.
• Who did you root for and why.
• Any place you had to reread to follow time or place.
• Lines that rang false in dialogue.

Mini test for Look Inside

• Ask three readers to stop at the moment they would sample out on a store. No warning. Record the page. If two stop before page 8, revise the opening.

Production sanity: no loose screws

• Front matter clean. Title page, copyright, dedication, acknowledgments as needed.
• Back matter clean. Author note, series list, newsletter link, next-book teaser, all links live.
• ISBN and metadata correct. Author name matches your tax and store accounts. Categories and keywords set with intent.
• Book description polished for the store page. First two lines hook on mobile.
• Cover and interior aligned with genre norms. Fonts readable. Section breaks clear. TOC works. No widows or orphans in the print proof.

Quick preflight

• Proof on e-ink, phone, tablet, and one printed copy. Different screens expose different sins.
• Click every link in the back matter. Twice.
• Zoom to 200 percent on the EPUB. Look for odd punctuation spacing and stray characters.

Decision cues to publish without an editor

• Low-stakes project. Serial, reader magnet, pen name test, or a short read.
• Strong critique network. Two or more reliable partners who flagged issues early.
• Clear beta consensus. Feedback agrees on fixes you already implemented.
• You plan to update fast post-launch. File management sorted, v1.1 ready within a week if needed.

If all four fit, a careful self-directed launch makes sense.

Decision cues to delay and hire

• Debut novel or first in series.
• Complex timeline or mystery plotting where clue logic must hold.
• Nonfiction with legal, medical, or high-liability claims.
• Memoir with ethical or privacy concerns.
• Plans for wide print and distribution through IngramSpark or libraries.

If two or more apply, bring in a pro for at least one round.

A simple scorecard

• Give one point for each “publish” cue you meet.
• Give one point for each “delay” cue you meet.

If publish points win by two or more, proceed with a soft launch. If scores tie, hold. If delay points lead, hire help.

If proceeding: a safe launch plan

• Soft launch to your list first. ARC team and newsletter, no ads yet.
• Watch early reviews for quality signals. Typos, confusion, pacing notes, dialogue complaints. Track in a log.
• Fix fast. Update the master file, push a v1.1 within days. Thank early readers who flagged issues.
• Open ads only after reviews stabilize above the line for your genre.

A quick script for your update note

• Subject: Quick update to [Book Title]
• Body: Thanks for reading. A few reader notes helped me tighten [X and Y]. The file now reflects those fixes. If you downloaded earlier, hit your store library to refresh.

If delaying: productive waiting

• Book the right editor now. Ask for an assessment or a partial if budget is tight.
• Use the wait to level up the draft. Run another read-aloud. Recheck the reverse outline. TTS one more time.
• Expand the style sheet. Add knotty words, character ticks, series lore, and a timeline-by-chapter table.
• Run one more beta round on revised opening pages. Confirm grip before the edit slot starts.

Final gut check

Ask three hard questions

• Do I know where readers might bail, and did I address those spots.
• Do I have proof of clean pages on multiple devices.
• Am I ready to push fixes fast if early feedback points to trouble.

Three yes answers signal readiness. Anything less, slow down. No one remembers a late book that reads clean. Everyone remembers a rushed one that trips on page two.

Frequently Asked Questions

Download FREE ebook

Claim your free eBook today and join over 25,000 writers who have read and benefited from this ebook.

'It is probably one of the best books on writing I've read so far.' Miz Bent

Leave this empty

Get free book