Update docs/monthly-meeting/2024-03.md

Co-authored-by: Hugo van Kemenade <[email protected]>

Author: Unique-Usman

docs/monthly-meeting/2024-03.md

@@ -36,7 +36,7 @@ Please take a second to read through it!
   - Carol Willing: [Changelog splitting/reduction](https://github.com/python/docs-community/issues/98). At the February meeting, we had consensus that slimming down the changelog makes good sense. Let's discuss the potential approaches to do so, and try to reach consensus.
   - CAM: split by minor release (feature version) would probably make most sense; we could make it more granular.
   - Instead of changelog file we could have a changelog directory. Or we could chunk it in the directive. Either way is relatively straightforward.
-  - Ezio: We have to thing about the use of this changelog; one of those is searching for a particular module/function across all the releases. If we split it in several files, this'll be harder. Maybe we should keep a few latest releases on a single page. Or use tabs and make filtering faster.
+  - Ezio: We have to think about the use of this changelog; one of those is searching for a particular module/function across all the releases. If we split it in several files, this'll be harder. Maybe we should keep a few latest releases on a single page. Or use tabs and make filtering faster.
   - Hugo: On mobile, the page doesn't render well.
   - CAM: Are people searching the rendered HTML, or other files. (Petr: i use Ctrl+F quite often)
   - Carol: One more use case: When a bug happens, searching for when the feature was introduced.