Need to document the "Add general comment" option that you recently added.

Might be good to link to the Publish Options section on the Managing and publishing drafts page.

Just my own personal preference, but I think it'd be nicer to say "By default, the banner will be in grouped mode and control all active drafts"

Instead of "the multiple mode" you should say "the grouped mode", to be more consistent with the wording used above.
Also shouldn't the :guilabel: on this line be "Publish All" instead of "Publish"?

I think we should also mention general comments here some how.

Since you're here could you fix this typo: "have" -> "has"

The publishing-reviews page is gone now, so this will need to be updated.

This is a bit outdated, since you're here could you fix it up. To reply to a comment in a review, you click on the "Reply" button that's under the comment.
You can also make a general reply to a review, not linked to a comment. If the review does not have a header, there's a "Comment" button displayed at the top of the review that you can use to write a reply. If the review has a header, there is no "Comment" button, instead there is a "Reply" button under the header that you can use to write the reply.

I think you should mention how you can select individual replies from the banner. Could mention discarding here too.

Looks good :)

Just forgot an "and" here: "... in grouped mode and control all ..."

This looks great. There's a couple small consistency things, but the big-ticket items are less about this change and about our docs as a whole going forward, with an eye toward SEO.
Google rewards clear, concise paragraphs that are focused on a topic, and bullet points for options pertaining to leading text. Basically, if it eases scannability when reading content, it can benefit search results. Smaller paragraphs, shorter sentences, less complexity, visual separation, consistent naming, and consistent linking to topics can all help.
We have a lot of opportunities to make this happen in our docs. When we have a list of choices or multiple concepts/options for something in one paragraph, we should consider breaking them out into multiple paragraphs or bullet points.
(In general, bullet points seem to be rewarded these days.)
I pointed out a couple spots I think could convert well to that.

This should be in Title Case.

This is somewhat orthogonal to this change, but I wanted to take the opportunity to bring this up.
Something I'd like to start doing with our public documentation is properly naming aspects of our product and capitalizing them whenever we refer to them.
For example:

"Review Dialog" instead of "review dialog"
"General Comment" instead of "general comment"
"Draft Banner" instead of "draft banner".

These are specific entities in our product we're referring to. It's not a review dialog, it's the Review Dialog.
This would help them visually stand out in text and in search results, help with scanning for text, and hopefully help readers build a mental map of what's what in the UI.

This should be Title Case.

This should be Title Case.

This is a good paragraph to break into bullet points (helps with SEO and scanning of text). Any time we're describing multiple options Something like:

When the banner is in grouped mode, you have the following options for publishing:

* To publish all active drafts and blah blah, click :guilabel:`Publish All`.
* To publish or discard blah blah ...


The more we can do this, laying out options or steps or multiple choices in list form, the better our chances for Google to turn them into smarter search results. Also, just helps break up sections full of paragraphs.

Let's link to the Integrations page here for "chat services".

Let's use :guilabel: here for "Publish" button.

We don't have a page on archiving explicitly, but we have a dashboard page. That's maybe the best option for now. Let's link to it: star-archive-and-mute.

Extra blank line at the end of the file.

The comma feels a bit awkward here. Maybe:

Adding comments (General Comments, Diff Comments, or File Attachment Comments) will ...


With refs to each of the sections.

This could be simplified just a bit:

You can also reply to the review as a whole by clicking Reply under the review header. If there is no header text, ...

This contains many different useful instructions. I think we should break the paragraph at "To publish your replies".

Looks like this slipped in?