#and if you don't edit and post direclty well power to you i have typos every 3 words so i always do at least one read over khfdkjs

[bahoreal]

jay's wee guide to editing fics

by popular demand (five likes on a post i made asking if anyone wants this)

please note this is a loose guide of what works for me and is designed to give newbie fic writers an idea of what purpose an edit has. if you don't vibe with it you don't have to follow it. if you have your own preferences please feel free to add them!

first i should say it is important to do an edit before you post your fic. this can apply to any work of writing (some of the QC details I used a lot in the scientific papers i wrote)

an edit can be generally categorised into one of these: update/style check, QC, consistency check, proofread. this can either be done by you (the writer) or by a beta reader

update/style check: there's probably a better word for this kind of edit but I don't know it. This the most in depth and time consuming method of editing and generally done on first drafts. it is an edit done where you're not happy with the work to be published as-is, where you think parts are missing, parts could be updated, parts might be out of sync or not fit with the flow of the piece. when you're doing an update edit, you should be looking for things like:

- did this feel jarring against the rest of the tone

- did i have to read any of the sentences multiple times to figure out what they meant

- do I have enough elements that reflect the theme i'm trying to build, or was the theme too on the nose?

- are my characters behaving in character

- are there any points where a character knows about something before it has been confirmed in the text - is this intentional, or was it a mistake and the character shouldn't know? This is especially important with longer fics, sometimes the timeline can get messy

note for beta readers/if you are using a beta reader: specify whether this edit is meant to be granular to word choice, or about sentence/paragraphs. I have had beta readers that changed every fifth word I wrote because they thought a different word would fit better (which switched my story to their style, which I didn't actually want), and beta readers who would highlight a sentence or a word and go "this doesn't make sense, consider rephrasing" or a paragraph and go "this felt cut short" o.e. (which was very helpful)

QC: quality check. generally refers to formatting, updating to a style guide, etc. When I am doing a QC I look for things like

- grammar issues (non-intentional)

- typos (non-intentional)

- spelling mistakes (non-intentional)

- language consistency, e.g. going between England English and American English (non-intentional)

- formatting errors (e.g. I tend to add three paragraph breaks between new scenes, and I check that that's consistent throughout)

- tense consistency (switching back and forth between tenses when writing can break the reader out of the immersion, if you're in the present then try to stay in the present unless the character is remembering something. Instead of "She has nothing in the house. She went to the shops.", try and stick to one tense, "She has nothing in the house, so she goes to the shops.")

(- in papers/essays this is also the point where you would fix your referencing)

proofread: a final check done on a final draft that combines the QC and consistency checks. If i've copied to ao3 I tend to do this in the ao3 word editor and make sure all my formatting is in, for example italics, which aren't preserved in the copy/paste into the ao3 editor

consistency check: does what it says on the tin. If there are consistency items you want to keep flowing through your story, such as

- a character calling another character by a certain nickname and then progressing to a different nickname as you move through

- names used in internal monologue are consistent throughout, vs. names other characters use in speech (e.g. I wrote a fic from the perspective of an american, who says "couch", but the english characters say "sofa" aloud.)

- was that character holding a glass? where did it go? were they suddenly on the other side of the room?

- are the times/days correct? was it summer one scene and winter the next? if time is referenced, is it passing appropriately? (also ensuring it's non-intentional, unreliable narrators can switch between times as a stylistic choice)

(- in papers/essays this is also the point where I would make sure my claims are substantiated in the references I have used)

The things to look for are non-exhaustive. In my fics, I tend to do one single edit that combines all of these, or one update/style check and then a proofread if it's a long fic. This is because I don't tend to spend a lot of time on fics. with my original works, I tend to do each check individually, with the update/style check first, then a consistency check, then a QC, then the proofread. 4 drafts (at least, sigh)

A beta reader can help with some of these, especially the consistency check and the update/style check - when you read your own work a lot you do tend to miss things. However I cannot stress enough when you are asking a beta reader to look over your work, set your expectations:

tell them which kind of edit you'd like them to do. If you want a QC and you get back a style check it can feel a little insulting

if you want a more thorough edit like a style check or a consistency check then set expectations for the level of edit. If you want to develop your own style of writing, then specify you don't want your beta reader to be too picky over word choices, only calling out if, e.g. words don't make sense in context. If you want a language check (maybe your first language isn't english and you are worried about writing in english) then ask for more detailed notes on your specific word choice. it's entirely up to you, and knowing what is expected of them can make the beta's job easier!

And some things personal to me:

items/advice about how i write my own fic, these are things I look for in the update/style check to ensure the conclusion is built to in a satisfying way

plot themes, and building callbacks: I like to pick a few callbacks for my characters and have them mentioned a few times throughout the story - enough that readers will notice and appreciate the callback, but not too much that it's all the characters talk about. it's a delicate balance and depends on the length of the fic and the themes you choose. for example in the longfic i'm writing I have romcoms as a theme, where the characters bring up their favourite big romcom lines a couple of times, then joke around finding their own when they finally kiss. in my original novel i have one fun theme of one of my characters absolutely loving bread and always eating it whenever there's bread offered, and also a plot related theme of discussion about poison, poison preparation, and contemporary medical diagnoses of poisoning which leads a character to realise [REDACTED] might have been poisoned (these things are unrelated my character does not die of poison bread lmao) sometimes these callback themes can reflect the plot of your fic, or it can be a fun character thing that keeps coming back, or it can reflect how a character has grown from the start of the story

characterisation through your story: I'd suggest figuring out where your character starts, and the growth you want them to go through to make the characterisation more fulfilling. this can just be something specific you want that character to realise, or the character settling into the role they have and realising they enjoy it and fighting back less, or a character striving for something and either getting it or not getting it and deciding whether they even wanted it, etc. sometimes the simpler the fundamental character arc, the better. it can help with linking the character arc to the plot, and figuring out how minor characters are doing in the background of the fic

have fun and enjoy! don't feel obligated to follow my advice exactly or stick rigidly to one of the edit types, having a mix between them is just as useful and sometimes certain items slip from edit to edit! sharing your work is scary, but knowing you've picked up on typos and minor errors before you share can reduce that fear a bit :)