It happens to the best of us. I have nearly thirty years experience as a professional proofreader and copyeditor, and I doubt that a single one of my stories is completely error-free. At a certain point I skipped the "Read Aloud" tool, and that made it even worse.
I'm going to be a pedant and point out that this is a solved problem, and that components that can do this have been widely available for quite some time. There's no need for Lit's army of tame Lemurs to write their own when they could choose a well-supported, feature-rich, likely open-source component to do it for them.
That's a big fear I have when publishing. One solution is to walk away from the finished product and let it sit, to give time for new ideas to trickle in. But I don't want to sit on the thing forever either--I'm too excited to share it!
Happens to me all the time. Laurel probably hates me for how often I post edited chapters. They take a long time to post. Just submit and try to forget! Good luck!
Given the number of "solved problems" the site has, it's extremely doubtful that it was built on a purchased package. Much more likely it grew organically from a home grown system. It has been tinkered with, but as with any bag of potatoes, you push in a lump somewhere, and a new lump appears elsewhere...
Yep! I'm trying to exercise more patience in this regard.
Some writers have taken stories down and published updated versions as new.
I've considered this, but the last thing I need is to take a story down only for it to get false-positived as AI or some other nonsense when I try to submit the updated version. I'm better off just living with the missed opportunity.
I made some pretty heavy revisions to Scale Servicing. I liked it and wanted to like it more. In the interest of transparency, I put a note at the top with a date indicating as such. I was hesitant to repost it because I didn't want followers to think, "Oh, this one again?" But I could also see a legitimate case for doing so too.
