Skip to content

Commit 2428309

Browse files
committed
Spelling
1 parent 21ecd67 commit 2428309

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/monthly-meeting/2025-04.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ Example topics for discussion:
5858
| Language | 30 days progress |
5959
| -------- | ------------------ |
6060
| Brazilian Portuguese | +0.91% |
61-
| Simplifed Chinese | +0.56% |
61+
| Simplified Chinese | +0.56% |
6262
| Romanian | +0.30% |
6363
| Russian | +0.20% |
6464
| Japanese | +0.16% |
@@ -95,7 +95,7 @@ Example topics for discussion:
9595
- General agreement for a light-touch & pragmatic approach to managing language coordinators,
9696
for example approving any coordinator nominated by a core developer, or a similar policy.
9797
- Translations fall within the Editorial Board's remit, so they might decide a policy statement.
98-
- Stan has suggested some changes to PEP 545 on [Discourse](https://discuss.python.org/t/83534) about tranlsation management (dealing with inactive translators), translation quality (mass pushing of poor quality machine translations) and improving methods of finding translators (All currently awaiting SC review) and another [Discourse](https://discuss.python.org/t/75750/3) on switcher requirements (inconclusive),
98+
- Stan has suggested some changes to PEP 545 on [Discourse](https://discuss.python.org/t/83534) about translation management (dealing with inactive translators), translation quality (mass pushing of poor quality machine translations) and improving methods of finding translators (All currently awaiting SC review) and another [Discourse](https://discuss.python.org/t/75750/3) on switcher requirements (inconclusive),
9999
but these weren't discussed due to audio problems.
100100

101101
### Ensemble contributor session
@@ -126,7 +126,7 @@ Example topics for discussion:
126126
- Ned notes that a frequent blocker is that a seemingly small change can represent a philosophical decision, which take time to reach consensus on.
127127
Experienced reviewers can spot these types of change quite quickly. How do we communicate this to new contributors?
128128
- It is disheartening to have a first PR languish unreviewed, or have 70 comments of back-and-forth debate.
129-
- Hugo noted the examplar of the *string examples* PR, seeking to add an example snippet to each `str` method.
129+
- Hugo noted the exemplar of the *string examples* PR, seeking to add an example snippet to each `str` method.
130130
This is unreviewable with everything in one PR, but e.g. splitting to many small PRs might help refine the process.
131131
Just a single change request blocks an entire PR, whereas smaller PRs are easier to merge quickly.
132132

0 commit comments

Comments
 (0)