@aduh95 thanks, (I thought author-ready implies CI started though?)

I thought author-ready implies CI started though?

For doc-only changes, GH Actions are enough to land.

Good to know, thanks 🙏

Apparently this is also fine to fast-track according to:

Focused changes that affect only documentation

So 👍 to fast track if you think this is fine to fast-track :]

nit: then fulfills feels a little abrupt in these sentences. Should we prepend an and or a , to make it sound better?

@RaisinTen I don't mind making a follow up PR auditing the documentation further - I think certain ways we phrase things isn't really super helpful:

For example stuff like

#### `filehandle.chown(uid, gid)`
<!-- YAML
added: v10.0.0
-->

* `uid` {integer}
* `gid` {integer}
* Returns: {Promise}

Changes the ownership of the file then fulfills the `Promise` with no arguments
upon success.

Probably should be:

#### `filehandle.chown(uid, gid)`
<!-- YAML
added: v10.0.0
-->

* `uid` {integer} The file's new owner's user id.
* `gid` {integer} The file's new group's group id.
* Returns: {Promise} Fulfills with `undefined` when the operation has completed.

Changes the ownership of the given file. A wrapper for chown(2).

If I make such a PR would you be up for reviewing?

Landed in 271e04f

@benjamingr that looks much better. Sure, I will. :)