So, the rule is that if you have a single character speaking across multiple paragraphs, you don't use end quotes on those paragraphs. I get the intent of the rule, but I think it looks awful and is jarring.

What I have been doing for a long time, is to insert a minor action at the end of that paragraph or the start of the next. I don't even notice that I am doing it anymore, it just feels natural to have a character gesture or emote in some way every so often.

The only reason that this came to mind is that one of my new readers pointed out a spot in Chapter 50 where I had used end quotes on a paragraph break of continuous speech. I edited in a minor action instead, the character was recalling a previous thought process, so I had him lean back in his chair and look up, which is the sort of thing people often do during that sort of thought.

One of the advantages of publishing a serial online, you potentially get some good feedback. :)

I've had this happen twice now, though the first time I didn't know what was going on, the second time it happened the change was much more visible.

So, while I am in the middle of writing a reply to Post A, the post is replaced with a different post in the same community. However, the comments remain the comments for Post A, despite the section at the top having been replaced by Post B.

Yes, this means on one page I have the post itself for Post B, and the comments section/replies for Post A

It is very confusing and distracting when this happens.

So, Grammarly is correcting me a lot on a phrase I tend to use, and I don't entirely understand the difference.

On a sentence that expands upon a previous sentence in dialog, I tend to have a character say "Which means [...]"

Grammarly wants to fix this to be "This means [...]"

It's become clear to me that I tend to use 'which' instead of 'this' when speaking, but I am not sure why one is preferred use over the other.

Can anyone offer me some insight? I already tried googling "which vs this", but I got results for "which vs that" instead, which is an entirely different use case.