Update developer release guide to follow conventions

[0taj]

PR summary

Updated the developer release guide to follow the matplotlib formatting standards and conventions (https://matplotlib.org/devdocs/devel/document.html#section-formatting). This PR closes one of tasks listed in the issue #26862

PR checklist

• "closes #0000" is in the body of the PR description to link the related issue
• [N/A] new and changed code is tested
• [N/A] Plotting related features are demonstrated in an example
• [N/A] New Features and API Changes are noted with a directive and release note
• Documentation complies with general and docstring guidelines

[github-actions]

Thank you for opening your first PR into Matplotlib!

If you have not heard from us in a week or so, please leave a new comment below and that should bring it to our attention. Most of our reviewers are volunteers and sometimes things fall through the cracks.

You can also join us on gitter for real-time discussion.

For details on testing, writing docs, and our review process, please see the developer guide

We strive to be a welcoming and open project. Please follow our Code of Conduct.

[story645]

Thanks for the contribution, one small change to make :)

[QuLogic]

Please use a more descriptive PR title/commit message than GitHub's default, in the future.

Change was made

[QuLogic]

Thanks @0taj! Congratulations on your first PR to Matplotlib 🎉 We hope to hear from you again.

PS, your macbook is committing with junpeiota@Junpeis-MacBook-Pro.local; you probably will want to configure your git to use your real email address (or the hidden one that GitHub provides)