diff --git a/documentation/blog/2025-04-22-community-bestcodes/index.md b/documentation/blog/2025-04-22-community-bestcodes/index.md
index 28f815b86886..9eb95ddbd93a 100644
--- a/documentation/blog/2025-04-22-community-bestcodes/index.md
+++ b/documentation/blog/2025-04-22-community-bestcodes/index.md
@@ -13,7 +13,7 @@ The only way to discover how much of an impact your contributions can make is to
 
 ## How BestCodes Discovered Goose
 
-[BestCodes (aka William Steele)](https://bestcodes.dev/) first discovered Goose during a [GitHub Open Source Friday livestream](https://www.youtube.com/watch?v=O-zJJN-TkXc&ab_channel=AngieJones) and decided to give it a try. At the time, Goose offered limited support for Windows/Linux (with more work in progress before any official release). Since BestCodes wasn't a Mac user, he wanted to help bring support to Linux. After lots of troubleshooting, he ended up creating [a Debian build fix](https://github.com/block/goose/pull/2070) that finally let him start using Goose on Linux. 
+[BestCodes](https://bestcodes.dev/) first discovered Goose during a [GitHub Open Source Friday livestream](https://www.youtube.com/watch?v=O-zJJN-TkXc&ab_channel=AngieJones) and decided to give it a try. At the time, Goose offered limited support for Windows/Linux (with more work in progress before any official release). Since BestCodes wasn't a Mac user, he wanted to help bring support to Linux. After lots of troubleshooting, he ended up creating [a Debian build fix](https://github.com/block/goose/pull/2070) that finally let him start using Goose on Linux. 
 
 Even though BestCodes wondered if such a small fix was worth sharing, it was this "small" contribution that enabled fellow community members wanting to use Goose on Linux, and gave him momentum for future PRs. His experience is proof that your contribution has a chance to help someone, and you should share it! You never know what curiosity and the open source community can make happen.
 
@@ -39,4 +39,4 @@ Interested in contributing to goose and having your work featured? Whether it's
   <meta name="twitter:title" content="How One Contribution Can Spark Many Wins" />
   <meta name="twitter:description" content="The snowball effect of one contributor's small fixes" />
   <meta name="twitter:image" content="https://block.github.io/goose/assets/images/bestcodes-3d6c50de10a2d84def19d515aaea0724.png" />
-</head>
\ No newline at end of file
+</head>