Apply suggestions from code review

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

Author: egeakman

docs/monthly-meeting/2023-07.md

@@ -2,7 +2,7 @@
 
 - **Date:** 2023-07-03
 - **Time:** [19:00 UTC](https://arewemeetingyet.com/UTC/2023-07-03/19:00/Docs%20Meeting) 
-- **This HackMD:** https://hackmd.io/@encukou/pydocswg1
+- **This HackMD:** [https://hackmd.io/@encukou/pydocswg1](https://hackmd.io/@encukou/pydocswg1)
 - [**Discourse thread**](https://discuss.python.org/t/28736) (for July)
 - [**Meeting reports**](https://docs-community.readthedocs.io/en/latest/monthly-meeting/index.html) (the latest one might be an [**unmerged PR**](https://github.com/python/docs-community/pulls))
 - **Calendar event:** (send your e-mail to Mariatta for an invitation)
@@ -29,8 +29,8 @@ Please take a second to read through it!
 ## Discussion
 
 * Thoughts on MDN icons (see e.g. the ToC sidebar for [Document](https://developer.mozilla.org/en-US/docs/Web/API/Document)), as a compact way to flag API status in overviews?
-    * :wastebasket: = deprecated
-    * :warning: = non-standard/implementation-specific
+    * 🗑️ = deprecated
+    * ⚠️ = non-standard/implementation-specific
     * 🧪 = experimental/unstable
 
 * Programmatic handling of `deprecated-removed`
@@ -42,7 +42,7 @@ Please take a second to read through it!
 * Thoughts on putting a translation progress notice in docs pages (for each language)? [python/docsbuild-scripts#148](https://github.com/python/docsbuild-scripts/issues/148)
     * Sounds like a good idea
     * Sphinx issue is open
-        * This should be done in Sphinx first - Manuel will look into it (https://github.com/sphinx-doc/sphinx/issues/11157)
+        * This should be done in Sphinx first - Manuel will look into it ([sphinx-doc/sphinx#11157](https://github.com/sphinx-doc/sphinx/issues/11157))
     * Spanish docs have a [neat progress page](https://python-docs-es.readthedocs.io/es/3.11/progress.html)
         * Should we add it to all translations?