diff --git a/src/content/blog/release-v1.23.5-auto-port-assignment.md b/src/content/blog/release-v1.23.5-auto-port-assignment.md
index 331e5a7a..ffeb8c88 100644
--- a/src/content/blog/release-v1.23.5-auto-port-assignment.md
+++ b/src/content/blog/release-v1.23.5-auto-port-assignment.md
@@ -15,8 +15,7 @@ I'm happy to announce that [DDEV v1.23.5](https://github.com/ddev/ddev/releases/
 
 **Automatic Port Selection**: In the past, when you started up a DDEV project and the configured ports were already in use, you got an error message. This was [easy to work around](https://ddev.readthedocs.io/en/stable/users/usage/troubleshooting/#web-server-ports-already-occupied), and easy to configure for your system, but it was an unnecessary stop on people's DDEV journey, especially for first-time users. Now, DDEV automatically selects an available port in this situation, and just continues starting your project using the available port. Have apache running? No problem. Have Lando running? No problem. You'll probably want to use the default ports 80 and 443 as you go forward, but there's no reason to stumble starting up a project for the first time. This ambitious and difficult feature was implemented by community member [Alberto Viu](https://github.com/agviu) and me and would never have happened without his initiative and expertise. Thanks!
 
-**Automatic Time Zones**: It's been possible to specify the time zone for the web container for years, but automating it was suggested by community member [Martin Anderson-Clutz (mandclu)
-](https://www.drupal.org/u/mandclu) in the Drupal slack and implemented by Stas. We think that it will "just work" for almost everybody.
+**Automatic Time Zones**: It's been possible to specify the time zone for the web container for years, but automating it was suggested by community member [Martin Anderson-Clutz (mandclu)](https://www.drupal.org/u/mandclu) in the Drupal slack and implemented by Stas. We think that it will "just work" for almost everybody.
 
 **`ddev get` becomes `ddev add-on`**: Community member [Guy Sartorelli](https://github.com/GuySartorelli) took this one on and nailed it. He noticed that `ddev get` had outgrown its name and now had too many weird permutations, so now we have `ddev add-on list` and `ddev add-on remove` and things that make more sense. Don't worry, the same capabilities are still there, and `ddev get` still works the way it did, it just nags you a little bit when you use the old command.