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

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

Author: Unique-Usman

docs/monthly-meeting/2024-03.md

@@ -78,7 +78,7 @@ Please take a second to read through it!
 
 - Erlend: Evaluate param markup for `eval()` in `Doc/library/functions.rst` (PR [#115212](https://github.com/python/cpython/pull/115212))
 
-  - Erlend: Last year (https://discuss.python.org/t/16090) there was a discussion about why we don't use markup for arguments. The consensus seemed to be "let's try it out". I did, and received mostly positive feedback. Now I changed `eval` needs more attention than some weird corner of the stdlib. I merged it; looking for feedback. I have more functions in the pipeline.
+  - Erlend: Last year ([https://discuss.python.org/t/16090](https://discuss.python.org/t/16090)) there was a discussion about why we don't use markup for arguments. The consensus seemed to be "let's try it out". I did, and received mostly positive feedback. Now I changed `eval` needs more attention than some weird corner of the stdlib. I merged it; looking for feedback. I have more functions in the pipeline.
   - Hugo: +1, it's easier to scan
   - Erlend: the issue had a very long history with lots of discussion about how to communicate the meaning of the parameters, before we agreed on a wording that everyone liked. Structured parameter docs make this easier.
   - Ned: I wish we could get away with the Sphinx syntax where colons are brackets somehow.