fix typo

(cherry picked from commit c9b0c47)

bridgetown-website/src/_posts/2024/2024-04-02-happy-birthday-bridgetown.md

@@ -20,7 +20,7 @@ I know we all sort of cringe thinking about Webpack today (_esbuild forever!_),
 
 It's interesting to look at my original notes on what was most urgent to add to whatever might emerge from this fork: Webpack (as mentioned), Components (not just basic includes/partials), Internationalization (i18n), and easier third-party API integration were top of the list. A promising start! But a lot of what I love today about Bridgetown hadn't quite been conceived of yet. **Much has happened in only four years!** (You can find a more in-depth [list of post-Jekyll features and changes here](/docs/migrating/features-since-jekyll) if you're curious.)
 
-One major direction for Bridgetown I imagined in those earlier days that we ended up totally shifting away from is a tight integration with Rails. Aside from my [own perspective on Rails shifting](/future/road-to-bridgetown-2.0-escaping-burnout/), it turns out a significant level of interest in the potential architecture such a marriage might produce never materialized. I could do a deep dive some day into why that might be, but the good news (and a direction I never would have foreseen in 2020!) is that we pivoted into a tight integration with [Roda](/docs/routes). That proved to be a **huge boon** for the framework—with a lot of newer features being heavily inspired by the "Roda way" like the new [Initializers](/docs/configuration/initializers) system—and **I'm ready to push that all to the max this year**. I see no reason why, with just a tad more DX polish, a combined Bridgetown + Roda couldn't be then used to build _substantial_ web applications serving thousands of customers. I look forward to spreading the message that Bridgetown is far more than "just" a static-site generator (as we clearly say right on our homepage!) by promoting solid integrations with [Rodauth](http://rodauth.jeremyevans.net) and [Sequel](http://sequel.jeremyevans.net) to round out our server-side offerings. (We're basically just living in the RECU—the Jeremy Evans Cinematic Universe—at this point! 😅)
+One major direction for Bridgetown I imagined in those earlier days that we ended up totally shifting away from is a tight integration with Rails. Aside from my [own perspective on Rails shifting](/future/road-to-bridgetown-2.0-escaping-burnout/), it turns out a significant level of interest in the potential architecture such a marriage might produce never materialized. I could do a deep dive some day into why that might be, but the good news (and a direction I never would have foreseen in 2020!) is that we pivoted into a tight integration with [Roda](/docs/routes). That proved to be a **huge boon** for the framework—with a lot of newer features being heavily inspired by the "Roda way" like the new [Initializers](/docs/configuration/initializers) system—and **I'm ready to push that all to the max this year**. I see no reason why, with just a tad more DX polish, a combined Bridgetown + Roda couldn't be then used to build _substantial_ web applications serving thousands of customers. I look forward to spreading the message that Bridgetown is far more than "just" a static-site generator (as we clearly say right on our homepage!) by promoting solid integrations with [Rodauth](http://rodauth.jeremyevans.net) and [Sequel](http://sequel.jeremyevans.net) to round out our server-side offerings. (We're basically just living in the JECU—the Jeremy Evans Cinematic Universe—at this point! 😅)
 
 ## In closing…