What would you like to be added:

Currently, some headings are also steps in procedures. The format is not consistent. We need the heading format made consistent per the Grafana documentation style guide.

This means both the step number format (Step 1., Step 2.) and that everyt

Not a big deal but a UX annoyance...

Bug description

On our production app, look at a dashboard

https://app.posthog.com/dashboard/267

Then click into 'unique real sign ups', which is a pie chart

You will land on a trends page shown as a line graph instead.

In my experience, far and away the primary reason to use DatabaseError::downcast_ref() is to check the constraint name. It would be nice not to have to downcast, though:

https://github.com/launchbadge/sqlx/blob/master/sqlx-core/src/error.rs#L146

 pub trait DatabaseError: ... {
    // existing methods omitted

    /// Returns the name of the constraint that triggered the error, if