Google Docs for book editors on Mac: suggestions, comments and proofing in the browser

Set up a manuscript in Google Docs on Mac

Start in the browser. Google Docs runs in a browser tab, so you open docs.google.com, sign in and find the file in Drive. Set up the document before you edit a single sentence. Most editing trouble starts with a file nobody prepared.

Check three things first. Who owns the file. Who can comment or edit it. Which language the book uses. The owner matters because the owner decides what stays. Permissions matter because suggesting needs comment or edit access. If the Suggesting option is missing, ask the owner to share the file as a Commenter or Editor.

1. Open the manuscript in Google Docs. If you started in Word, convert it first and check the file size.
2. Set the language for the book before the first edit, so the spelling check reads the right dictionary.
3. Turn on Suggesting before your first change, so no edit is silent.
4. Write your house style rules in a comment on the first line. Name the source, such as your publisher's style sheet.
5. Make a copy for each round of edits, so the file you sent stays intact.

The browser steps for the language setting are in How to change the document language in Google Docs on Mac. Work through the list once on a test file. Then the steps stay in your hands.

Suggest edits instead of typing over the author

Suggesting mode keeps the author's words visible. Your insertions show in a different color. Your deletions show as struck-through text. The author sees exactly what you changed, and can reply to each change. That is the point of the mode.

To suggest an edit, select the text and click the Suggest edits button in the right margin. If that button is missing, open the Editing menu at the top right and choose Suggesting. Then type as normal. Google records each change as a suggestion.

A worked example: one copyedit

Here is a common kind of edit. The sentence reads: The committee, which met on Tuesday, decided that the report would be delayed. You want to cut the word that and change would be to will be. Select the word that, then press Delete. The deletion appears struck through, with a suggestion in the margin.

Next, select would be, type will be, and check the result. The author now sees two suggestions. Each one can be accepted or rejected on its own. Add a short comment with the reason, such as Cut the filler, so the author has the context they need.

Read the paragraph once in full after you finish. A paragraph that looks right in the margin can still read badly as one sentence. Change it now, while the edit is still a suggestion and easy to revise.

Switch back to Editing only for changes that do not need review. A typo in the title page might qualify, if the author agreed to it in advance. Most copyedits should stay in Suggesting. The full steps are on the page for suggesting edits in Google Docs on Mac.

Google Docs shortcuts for copyediting on Mac

Learn a few ⌘ shortcuts before a long edit. Press ⌘ / to open the shortcut list inside Docs. These are the ones that matter most for copyediting. Learn the mode switches first, then the tools you use on every page.

• ⌘ ⌥ ⇧ X: switch to Suggesting
• ⌘ ⌥ ⇧ Z: switch to Editing
• ⌘ ⌥ M: insert a comment on the selected text
• ⌘ ⇧ H: open find and replace, for checking every use of a name
• ⌘ ⇧ C: show the word count
• ⌘ ⌥ X: run the spelling and grammar check
• ⌘ /: open the full list of shortcuts

Some third-party guides list other keys for Suggesting. Check Google's keyboard help page first. Then test each key in a throwaway copy before you rely on it during a real edit.

Start with ⌘ ⌥ ⇧ X and ⌘ ⌥ M. Add the rest when a task calls for them. A few shortcuts used every day beat a long list you forget by Friday.

Accept or reject suggestions one change at a time

The document owner decides what stays. You can review suggestions from the Comments panel, and accept or reject each one on its own. You can also go to Tools > Review suggested edits and click Accept all or Reject all. Use the batch options only after you read the changes.

Work in small batches. Accept the changes the author agreed to in the last round. Leave open questions as comments, not as edits. Then reject the rest. Reread each changed paragraph after a batch, because accepted changes stack up quickly.

Before a large batch, make a copy with File > Make a copy. You can name the copy, choose where it saves, and choose whether to copy comments or suggestions. Keep the copy before the batch, so you can show the author what changed and why. The steps for each option are on how to accept or reject suggestions in Google Docs on Mac.

Handle a long manuscript without hitting the limit

A single Google Doc holds up to 1.02 million characters, according to Google Drive Help. That limit matters for a long book with notes, an index and a bibliography. Check the size before the work starts, not after the edits are in.

Word count and character count are different. Press ⌘ ⇧ C to see the word count in Docs. The limit counts characters, so do not guess the character count from the number of words. Use the count to decide early whether the book fits in one file.

Split a long book into parts. Keep one file for each part, plus a master file with the table of contents and the front matter. Check the parts against each other for names and cross-references. The steps for a contents page are on how to add a table of contents in Google Docs on Mac.

Plain text and Markdown behave differently. A text document converted to Google Docs format can be up to 50 MB. Converting Markdown used to risk changing formatting and stripping comments, which is why the newer Markdown support matters. The Markdown section below covers it.

Save a template for each series or publisher

Templates save setup time. On the Docs home screen, click Template Gallery at the top right, then choose a template. A copy of the template opens. Some template features only work for work or school accounts. If you sign in with a non-Gmail work or school account, sign in to reach them.

Google's template help does not explain how to submit or make a custom template. You can still build your own. Clean up a finished file, remove the old text, keep the headings and styles, then save it in one shared folder. Name it for the job, such as Publisher house style, with the date.

For a series, keep one master file. Duplicate it with File > Make a copy for each book. Choose the option to copy comments or suggestions only when you need the old record. A clean copy starts fresh. The template steps are on how to create a template in Google Docs on Mac.

Comments and questions for the author

Use comments for questions. Use suggestions for changes. A comment asks the author to decide. A suggestion shows the change you want. Keep each comment to one question, so the author can answer in the thread. Select the text and press ⌘ ⌥ M to add the comment.

Name the question clearly. Write Is this the first census or the second census? instead of Check date. A clear question gets a faster answer. The steps are on how to add a comment in Google Docs on Mac.

Gemini in Google Docs for comment threads

Gemini in Google Docs can summarize comment threads, insert comments, draft replies and propose edits from reviewer feedback. These comment workflows only work for people with edit access. Google began rolling them out on July 28, 2026, and features can take up to 15 days to appear.

Treat Gemini output as a draft. A proposed edit still needs your reading, your style sheet and your judgment. Test the feature on a copy before you use it on a manuscript the author is waiting on.

Common mistakes book editors make in Google Docs

• Typing over the author's text in Editing mode. The author cannot see what you changed.
• Accepting all suggestions after one quick read. Accept in batches and reread each paragraph.
• Editing the only copy. Make a copy for each round, so you can go back.
• Sharing as Viewer. Suggesting needs comment or edit access, so you cannot propose changes.
• Skipping the language setting. The spelling check then flags words the book spells correctly.
• Letting comment threads pile up. Resolve each thread after the author replies.

In Word, the most common Track Changes complaint is how to view the document with changes applied, according to a 2023 ProofreadNow post. That post recommends the No Markup view. It does not mention Google Docs. Check Google's help for the view setting before you sign off on a clean copy.

Google Docs or Word for book editing on Mac

Word is still the standard many editors use. A 2024 Editors' Weekly post calls Microsoft Word the industry standard. The same post lists Google Docs among free word processors. Choose the tool your client expects, because the file format decides what the author can open.

PerfectIt is a Microsoft Word add-in. It corrects spelling and grammar, and it checks consistency in hyphenation, capitalization and punctuation. Editors often use it for a first clean-up pass. It does not run inside Google Docs, so plan a manual consistency pass in Docs instead.

If a client sends Word files, convert them, edit them, and send back the format the client asked for. Keep the original file untouched. You can then show the client what changed if they ask.

Markdown files in Google Docs

Google Docs can now open, edit and collaborate on Markdown (.md) files without changing the file type. Before that change, converting Markdown into Docs format could alter formatting and strip comments. Rollout began October 5, 2026, and features can take up to 15 days to appear.

For a nonfiction writer who drafts in Markdown, this keeps the source file intact. Check whether the feature shows on your account before you plan a workflow around it. Do not assume it is live everywhere yet.

Find, replace and check consistency by hand

Without PerfectIt, run your own consistency pass. Start with a list of names, places and terms from the first chapter. Search for each one with ⌘ ⇧ H. Step through each match and fix the spelling or capital letters that differ.

1. Make a list of names and terms from chapter one.
2. Search each term with ⌘ ⇧ H and count the matches.
3. Fix mismatches in Suggesting mode, so the author sees each fix.
4. Search for banned spellings from your style sheet.
5. Note open questions in a comment, not in the text.

Repeat the search for each chapter. The same name can appear with two spellings across a long book. Keep your list in a separate doc, so it survives the next round.

Where Lazur helps while you edit in Google Docs

Lazur is a voice assistant for the Mac that lives in the notch. It listens and looks at the screen only while you hold the shortcut. Hold ⌥ ⌘ and ask about anything on screen. Lazur answers out loud.

Ask where a control is, and Lazur draws a circle and a label around it. Ask how to do something, and Lazur guides you one click at a time, waiting for each click. It does not click for you. It does not edit your file or operate other apps.

Hold fn to dictate clean, formatted text at the cursor in any app. Dictation helps with long comments to the author, or with a note you would rather speak. Snippets, a personal dictionary and clipboard slots help with the names and phrases you use often.

Lazur drafts text and types it for you. Ask for a short email to the author about a missing permission, read it, then keep or change it. Research runs in Lazur's own Chrome tabs, with the Lazur for Chrome extension, and comes back with a summary and a report. Check any source yourself before you cite it.

Lazur is not a plugin or add-in for any app. It has no partnerships with any app maker. You use it alongside Docs, not inside it. Read the pricing page for plan options, or download Lazur for the Mac.

Edge cases to plan for before a big project

A Google Docs Community thread is titled stuck in suggestion mode AGAIN. Its replies are not verified here, so treat it as a sign that the problem happens, not as a fix. Check the Editing menu at the top right when a change does not show as a suggestion.

If the author sends tracked changes from Word, convert the file, then check that the changes survived. Do not assume they did. Open the Comments panel and count the suggestions before you start accepting anything.

Plan for two people in one file. Agree on who makes which kind of change. Assign one person to accept or reject, because the document owner holds that power. A plan prevents the surprise of a silent rewrite.

Next steps for your first editing session

1. Make a copy of a finished chapter and turn on Suggesting.
2. Make three small edits and leave one question as a comment.
3. Ask the author to reply, then accept one batch and reject the rest.
4. Save the file as a template after the round is done.
5. Use one Lazur command at a time until the steps feel normal.

If you want a baseline for dictation, run the typing speed test first. Then try dictation for one comment per chapter. Keep whatever saves you time, and drop the rest.