From 9e146b27adb448b35162c60c92304078e589bd09 Mon Sep 17 00:00:00 2001
From: Sarah Boyce <42296566+sarahboyce@users.noreply.github.com>
Date: Fri, 20 Sep 2024 17:04:39 +0200
Subject: [PATCH] [5.1.x] Made cosmetic edits to the Steering council docs.

Backport of 39de2e97a06d0317973b280bc159ca6f89fc64e3 from main.
---
 docs/internals/organization.txt | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/docs/internals/organization.txt b/docs/internals/organization.txt
index 9ba11f4aec..64349d76ab 100644
--- a/docs/internals/organization.txt
+++ b/docs/internals/organization.txt
@@ -169,7 +169,7 @@ The steering council is a group of experienced contributors who:
 
 - provide oversight of Django's development and release process,
 - assist in setting the direction of feature development and releases,
-- take part in filling certain roles, and
+- select Mergers and Releasers, and
 - have a tie-breaking vote when other decision-making processes fail.
 
 Their main concern is to maintain the quality and stability of the Django Web
@@ -210,10 +210,13 @@ who demonstrate:
   This history must begin at least 18 months prior to the individual's
   candidacy for the Steering Council, and include substantive contributions in
   at least two of these bullet points:
-  - Code contributions on Django projects or major third-party packages in the Django ecosystem
+
+  - Code contributions to Django projects or major third-party packages in the
+    Django ecosystem
   - Reviewing pull requests and/or triaging Django project tickets
   - Documentation, tutorials or blog posts
-  - Discussions about Django on the django-developers mailing list or the Django Forum
+  - Discussions about Django on the django-developers mailing list or the Django
+    Forum
   - Running Django-related events or user groups
 
 - A history of engagement with the direction and future of Django. This does