While you're at it and touching these anyway, you could normalize it to use thestandard heading levels in the devguide—basically, just moving everything up a level, IIUC. But that's strictly optional, of course.

I'm planning to address that in a separate PR. Let's do the headings first; I want these doc PRs to be concise.

I'm not sure adding the "How to" prefix is necessary on titles that already are framed as tasks, since it is somewhat redundant and repetitive, especially if/when the supersection title is changed to "How-to"—it is inherent than sections directly underneath a "How to" section describe "How to" do something.

Absolutely, but Diátaxis explicitly recommends such headings:https://diataxis.fr/how-to-guides/#pay-attention-to-naming

Regarding the "How to" prefix;perhaps we should put this PR on hold until we're through the Diátaxis workshop in August. There is no hurry to get this done anyways.

Absolutely, but Diátaxis explicitly recommends such headings:diataxis.fr/how-to-guides/#pay-attention-to-naming

Right, but that's for top-level pagetitles, and the section headings would still be worded in task-oriented "how to" form (e.g. "(How to) adapt Python types to custom SQLite values", rather than the proscribed "Adapting Python types to custom SQLite values" or "Python-SQLite type conversion", with the "How to" wording as the top-level parent section, just not also repeated again in every sub-section title underneath it.

I guess you're right; that makes sense. I'd still like to put this on hold until after the workshop.

Here's how Django has organised their How To chapter:

https://docs.djangoproject.com/en/4.0/howto/

Closing this, as most of the work has been done in other PR's. If we need to tweak headings, we can do so on a case-by-case basis.