Thanks for fixing it. OK from manpages.
Can you commit it yourself or should I do that (giving proper credit, of course)?

Looks good, approved!
Bump the .Dd for this content change when you commit it.

Looks good to me.

I think the indentation is still wrong. If you compare https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/writing-style-guide.html, the indentation in the <para> tags starts right below the first "a" of "para". If there is an open link (or whatever other tag that does not fit on one line), you indent by two more until that tag closes again.
In this case, you just un-indent your change by two to align below the first "a" of <para> (unless it is a link) and then you should be good.

Whitespace fix recommendation.

Oh wow, thanks for the extensive testing. Change approved!

Good catches, approved!

Approved for commit! Thanks for working on the PR.

Good to go! Thanks for making that change.

Thanks for this change. Is there a sentence stop missing in the man page change?

Excellent, approved for commit!

The <description> tag needs to be right after the sentence stop. And if that should overflow the line, then break it into the next line:
... is
FreeBSD.</description>

Looks good to me.

I found two instances of superfluous spaces. I think once they are fixed, we can go ahead and commit the man page.

Approved, thank you!

A minor change is needed, but then you can commit it and close the PR.

A few instances where there are extra spaces, but those are easy to fix.

OK, that looks good now. Thank you!

Another round of edits needed, but we're getting there. Thanks!

OK from manpages.

OK from manpages.

Sounds like a cool feature to have. Thanks for working on it.
The man page looks good!

Thank you for writing the man page!
I've found a typo. Can you run textproc/igor and "mandoc -Tlint" over the man page and see if they turn up any warnings?

ping?

Thank you for rearranging those. Maybe textproc/igor can help you a bit with the proper alignment or check the FDP primer for examples.
Let me know if you need help.

You can commit this one, too.

You can commit this one. Thanks!

Good to go. Thanks!

Ah, can you un-indent the lines below the description tag to align like the other entries? Thanks!

In D22474#492077, @rpokala wrote:

Split lines in the manpages at the start of new sentences. Thanks igor(1)!

Good to (literally) go!

I'm OK with the new text.

OK, thanks for fixing the indentation. Ready to go!

Approved!

Looks good, thank you!

Thanks for fixing. A package message seems good to me.
Other than that, users are required to look into that file or run "pkg updating".
Thinking about this a bit more, we could merge the "Press" and "News" columns on freebsd.org into one. That would give us free space for ports announcements from that file. Just a thought...

Typo fix

Two comments.

OK, go ahead. We'll figure out a more elegant solution separately.

Looks good, ready to go!

Minor correction to the man page and (this is new to me) the code.

Also accepted, thanks for the cleanup work, researching those entries!

Ah, good work. It's appreciated. We do a bad job of cleaning these up (and companies usually don't tell us when they go out of business).
A periodic link checker might help with that, but for now, I agree that removing these invalid entries is better. Approved!

Adding Glen for clarification: Does it make sense to add the 13-CURRENT entity in the file or will that change other references that are using it already?
I think using 13-CURRENT is the right thing to do here and as @mat pointed out, it is easier to just reference it rather than changing it every time the version of CURRENT changes.

Man page looks good to me.

Bump the .Dd when you commit. Thanks!

Approved!

OK, if we don't have an entity for 13 in there at the moment, I guess we have to either add it there or use your original proposed patch.

Looks good, approved!
Thank you.

Grammar suggestion for the man page.

I'm fine with the latest changes to the man page.

I think we have a variable for the current release: &rel.current;
Can you try that and see if the has the desired effect? That way, we don't have to touch that fine each time when there is a new CURRENT release branch.

I'd start the text right after the opening <description> tags and the closing tag right after the sentence stop after "Freenode".

Looks god to me, go ahead with the commit.

OK from manpages. Don't forget to bump the .Dd of the man page when you commit this content change.

Looks good, you can commit that with my approval!

Approved, go ahead!

Approved. Can you commit that change yourself or should I?
Thanks for picking this up.

Looks good. You can commit it with my approval!
Thanks!

OK from manpages.

Two suggestions.

OK from manpages. Thanks for working on this.

Thank you for the man page.

Sorry to keep you waiting. I'll commit this soon. Thank you!

OK from manpages.

The man pages look fine to me, thanks for writing them.

Looks good, although I'd add a note after it that some shells (like zsh) need to invalidate the ^ using \^.

OK, thanks for the man page fixes. It can be committed with the source change now.

Looks good to me, thanks. Do you want to commit that yourself or should a docs person do it (with the proper attributions, of course)?

Gut, kann committed werden.

Nur zwei Fehler gefunden, gut! :)

OK from manpages.

OK from manpages.

Thanks for the update to the handbook. I've found a couple of things that are fairly easy to correct.

I agree with Conrad here.

Small grammo, nothing major.

Looks good.

OK from manpages. Thank you!