Skip to content

Commit cec72f0

Browse files
committed
Fix typos
1 parent cc80dd2 commit cec72f0

File tree

6 files changed

+7
-7
lines changed

6 files changed

+7
-7
lines changed

docs/monthly-meeting/2022-04.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,7 @@ Discussion outside the meeting should be on the issues :)
114114

115115
### Bringing in new people
116116

117-
- When “herding cats”, play into people's exixting strengths/interests
117+
- When “herding cats”, play into people's existing strengths/interests
118118
- Give people smaller, manageable tasks.
119119
- [ ] **Petr**: think about how to generate manageable tasks
120120

docs/monthly-meeting/2023-06.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Regrets:
3636
## Reports and celebrations
3737

3838
* [CAM and Erlend's PyCon US talk is now up](https://youtu.be/nMekFX2CDVk)
39-
* CAM also pressented a derived version at his local Huntsville Python Users Group (HSV.py)
39+
* CAM also presented a derived version at his local Huntsville Python Users Group (HSV.py)
4040

4141
* PEPs site updated for better readability and performance: [python/peps#3132](https://github.com/python/peps/pull/3132)
4242

docs/monthly-meeting/2023-08.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ Please take a second to read through it!
5151
- [Hugo] Dark theme deploy: 3.11 RM Pablo said fine to deploy. To deploy, need to merge [python/docsbuild-scripts#161](https://github.com/python/docsbuild-scripts/pull/161) and/or pin in `requirements.txt`
5252

5353
- [CAM] Update on structured deprecation work
54-
- Originaly prompted by [a recent Discourse thread on soft deprecations](https://discuss.python.org/t/formalize-the-concept-of-soft-deprecation-dont-schedule-removal-in-pep-387-backwards-compatibility-policy/27957/73)
54+
- Originally prompted by [a recent Discourse thread on soft deprecations](https://discuss.python.org/t/formalize-the-concept-of-soft-deprecation-dont-schedule-removal-in-pep-387-backwards-compatibility-policy/27957/73)
5555
- Went through many iterations of design and testing on examples
5656
- Wrote up a [detailed design doc](https://hackmd.io/@CAM-Gerlach/BJuLFRLj2) with:
5757
- Rationale and benefits

docs/monthly-meeting/2023-09.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ Please take a second to read through it!
7474
- Next steps: CAM to write to Deb from the PSF with a summary of this discussion
7575

7676
- [Maciej] Translations platform – trying to initiate discussion ([Discourse thread](https://discuss.python.org/t/docs-translation-platform/29940))
77-
- Transifex has cut off shared memory (between projects) for open source tier, Rafael from Brazilian Portugese team implemented a workaround
77+
- Transifex has cut off shared memory (between projects) for open source tier, Rafael from Brazilian Portuguese team implemented a workaround
7878
- Weblate – based on Django, open license, used by PyPI
7979
- The POC of Python docs translations/Weblate integration is functional, I'm working on improving it
8080
- Python docs don't fit into free open source tier on Weblate – the initial proposition is 1500€/year (50% discount)

docs/monthly-meeting/2024-02.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -75,7 +75,7 @@ Please take a second to read through it!
7575
- [Carol] Improving clarity around HOWTO docs: https://github.com/python/cpython/issues/114976
7676

7777
[CAM] Could you explain what the older-style howtos were?
78-
[Carol] It goes back to Linux in the early days, when docs were scarce. Howtos were architecture discussions of how sonething was implemented, more like background on a topic -- explanations in Diátaxis terms
78+
[Carol] It goes back to Linux in the early days, when docs were scarce. Howtos were architecture discussions of how something was implemented, more like background on a topic -- explanations in Diátaxis terms
7979
[Ned] Maybe the section could be called "longer writings"
8080
[Daniele] I always call them *howto guides*: `HOWTO` sounds like an old-school passcode
8181
[Carol] Could we use local ToC trees to split up the section?

docs/monthly-meeting/2024-03.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -90,10 +90,10 @@ Please take a second to read through it!
9090
- Hugo: I think it's good.
9191
- Erlend: One aspect is that this simplifies writing the description. It's more normalized so there isn't so much space for discussion.
9292
- Petr: Maybe we could get a graphic designer comment on the theme.
93-
- Hugo: Tania Allard has offered to help with an accessibilty audit which could help
93+
- Hugo: Tania Allard has offered to help with an accessibility audit which could help
9494
- Ned: There are disparate styles: `str` is monospace, *code object* is italic
9595
- CAM: We had a big discussion about how to style `None`; decision was to use monospace but not link it. There are differences in the markup too.
96-
- Ned: Should we link `str` and `dict`? We could just use monospace. Sometimes, the docs canbe over-linked.
96+
- Ned: Should we link `str` and `dict`? We could just use monospace. Sometimes, the docs can be over-linked.
9797
- CAM: it's important to distinguish names that exist in Python.
9898
- Carol: Let's ask a UI expert.
9999
- (...)

0 commit comments

Comments
 (0)