Improve the sqlite3 reference, using [Diataxis as a guideline](https://diataxis.fr/reference/). A lot of work has already been done here, with great help from Alex Waygood and CAM Gerlach. PRs so far[^1] have focused on...: - [Be accurate](https://diataxis.fr/reference/#be-accurate) - [Do nothing but describe](https://diataxis.fr/reference/#do-nothing-but-describe); making the wording more to the point <details> <summary>Previous work over the last few years</summary> Both of these have been improved greatly by the following issues and PRs, amongst others: - gh-94630 - gh-95235 - gh-95235 - gh-94940 - gh-94321 - gh-94628 - gh-94017 - gh-93890 - gh-93925 - gh-87260 - gh-89018 - gh-92780 - gh-90923 - gh-30660 - gh-29326 - gh-29200 - gh-29219 - gh-28238 - gh-26220 - gh-25003 - gh-23159 - gh-23965 - consistency: gh-31772 - consistency: gh-24746 </details> There are remaining issues, though: - [x] Be accurate: - #95379 - #95523 - #95530 - [x] [Be consistent](https://diataxis.fr/reference/#be-consistent): Most of the reference docs for sqlite3 functions and methods use the imperative mood. Some of the methods use other wordings. Suggesting to normalise, and use the imperative mood across the reference section. Improved with: - #95274 - #95525 - Remove duplicate links - [x] [Respect the structure of the machinery](https://diataxis.fr/reference/#respect-the-structure-of-the-machinery): Arrange the sections of reference to follow the architecture of the module. This is pretty good already, but I believe we may benefit from some adjustments, in particular: - [x] Consistently group attributes and methods - #95626 - #95430 - Align wording in function and method docstrings with documentation - [x] [Do nothing but describe](https://diataxis.fr/reference/#do-nothing-but-describe): Avoid digressions and discussions, or even better, extract them to separate sections. Remove and or simplify examples. - #95351 - #95383 - gh-95840 [^1]: There have been too many PRs to list; some of them were done before Diataxis was even discussed.