Looks good to me. Approved!

This may be coming from the upstream vendor and may be fixed there already. When we import this third party software next time, we'll get this fix automatically. It is worth checking if it is fixed upstream. If not, they'll certainly appreciate a bug report.

Looks good to me, thanks!

OK for the man page part of the change.

Looks good, approved!

Other than that, it's OK to commit.

Checked up and good to go!

I'll take care of it. Thanks for the work!

OK for the man page change.

Man page looks good to me. The actual code has to be reviewed/accepted by someone else.

Looks good to me. I think we should try to use some automated link checker that reports when there is a broken link in our docs. But that's beside this review, so go ahead. Thank you for the work!

OK for the man page part of the change.

Some language and typo fixes.

Looks good to me.

Here's how you can "make" the doc tree:
https://docs.freebsd.org/en/books/fdp-primer/doc-build/

Small fixes, easy to implement..

Looks good to me.

Looks good to me, thanks!

yes, no more need for DocBook tools/validations since we moved to Asciidoc.

Ideally, this would list the browser used when testing. This is a quickly moving target as both browsers and meeting software evolve, we would need a couple more "works here" reports from users before we can make that claim in the handbook.

If you don't know any (or want to add) individual reviewers, you can use the reviewer groups you used.

Looks good, thanks for the submission.

We moved to Asciidoc a couple of years ago. It is doubtful that this patch will ever be committed. The content changes are good, but would need a new patch against our new doc tolchain.

Committed in https://cgit.freebsd.org/doc/commit/?id=cbe1572983c139a36fb0357e16df0dd01e1318ad
Forgot to reference this review and the PR. Will close the latter separately.
Thanks to everyone who provided input here.

I'll take care of committing this change soon.

net/cloud-init would be useful for cloud-y environments.

Looks good to me, thanks!

OK from manpages.

OK from manpages.

OK from manpages.

A few suggestions for improvements.

Looks good. When you commit, do a bump of the .Dd for this content change. Thank you!

OK for the man page change. Make sure to bump the .Dd when you commit it for this content change.
Thanks for working on this, it's appreciated!

Looks good now, thank you!

Only a minor nit, the rest looks fine. Thanks for the update!

OK from manpages.

Good to (literally) go!

You can also run vale on your doc to get some helpful output.

OK from manpages.

Looks alright, I think these are good additions.

Resolve the XXX instance. The rest looks good to me and I find it good to have such a document to detail the changes between major release versions.

OK from manpages

Typo

Why do you need a docs review for this?