chore: fix typos in latest blog post

Author: innocenzi

src/Web/Blog/articles/2025-03-24-alpha-6.md

@@ -1,6 +1,6 @@
 ---
 title: The final alpha release
-description: Tempest alpha 6 is released, we'll talk about Tempest's future and highlight the most important new features in this release 
+description: Tempest alpha 6 is released, we'll talk about Tempest's future and highlight the most important new features in this release
 author: brent
 tag: Release
 ---
@@ -13,19 +13,19 @@ composer create-project tempest/app:1.0-alpha.6 <name>
 
 ## Tempest's future
 
-Tempest's first alpha release was tagged half a year ago. It's amazing to see that, since then, 35 people have contributed to the project, and alpha.6 is so different and so much more feature-rich than alpha.1. At the same time, it's important to realize that we cannot stay in alpha for years. There is so much more to be done, and Tempest is far from "ready", but there's a real danger of ending in an infinite "alpha limbo", where we keep adding awesome stuff, but never get to actually release something for real.
+Tempest's first alpha release was tagged half a year ago. It's amazing to see that, since then, 35 people have contributed to the project, and alpha 6 is so different and so much more feature-rich than alpha 1. At the same time, it's important to realize that we cannot stay in alpha for years. There is so much more to be done, and Tempest is far from "ready", but there's a real danger of ending in an infinite "alpha limbo", where we keep adding awesome stuff, but never get to actually release something for real.
 
 I want Tempest to be real. And real things aren't perfect. They don't _have_ to be perfect. That's why we're now moving towards 1.0. There'll be one or two beta releases after this one, but that's it. The goal of these beta releases will be to fix some final bugs, review the docs, do some touch-ups here and there. The goal of 1.0 isn't to be perfect, it's to be real.
 
 There is one thing we've agreed on with the core team: we'll mark some components and features as _experimental_. These experimental features can still change after 1.0 in minor releases. This gives us a bit more freedom to iron out the kinks, but also gives Tempest users some more certainty about what's changing and what not. The goal is to have this list ready before beta.1, and then we'll have some more insights in whether there are possibly future breaking changes or not.
 
-All of that being said, let's talk about what's new in Tempest alpha.6!
+All of that being said, let's talk about what's new in Tempest alpha 6!
 
-## tempest/view updates
+## `tempest/view` updates
 
-We start with tempest/view, which has gotten a lot of love this release. We've fixed a wide range of edge cases and bugs (many were caused because we switched to PHP's built-in HTML 5 spec compliant parser), but we also added a whole range of cool new features.
+We start with {`tempest/view`}, which has gotten a lot of love this release. We've fixed a wide range of edge cases and bugs (many were caused because we switched to PHP's built-in HTML 5 spec compliant parser), but we also added a whole range of cool new features.
 
-### x-template
+### `x-template`
 
 There's a new `{html}<x-template>` component which will only render its contents so that you don't have to wrap that content into another element. For example, the following:
 
@@ -54,7 +54,7 @@ View components now have direct access to the `$slots` and `$attributes` variabl
 ```html
 <x-component name="x-tabs">
     <span :foreach="$attributes['tags'] as $tag">{{ $tag }}</span>
-    
+
     <x-codeblock :foreach="$slots as $slot">
         <h1>{{ $slot->name }}</h1>
 
@@ -106,7 +106,7 @@ final class BookController
     public function index(): View
     {
         // book_index.view.php can be in the same folder as this directory
-        return view('book_index.view.php');  
+        return view('book_index.view.php');
     }
 }
 ```
@@ -157,17 +157,17 @@ View components can now be discovered by file name:
 </x-base>
 ```
 
-### The x-icon components
+### The `x-icon` component
 
-And finally, there's a new `{html}<x-icon>` component which adds built-in support for [iconfy](https://iconify.design/) icons:
+And finally, there's a new `{html}<x-icon>` component, added by {gh:nhedger,Nicolas}, which adds built-in support for [Iconify](https://iconify.design/) icons:
 
 ```html
 <x-icon name="tabler:rss" class="shrink-0 size-4" />
 ```
 
 ## Primitive helpers
 
-Enzo has made some pretty significant changes to our `arr()` and `str()` helpers: there are now two variants available: `MutableString` and `ImmutableString`, as well as `MutableArray` and `ImmutableArray`. The helper functions still use the immutable version by default:
+{gh:innocenzi,Enzo} has made some pretty significant changes to our `arr()` and `str()` helpers: there are now two variants available: `MutableString` and `ImmutableString`, as well as `MutableArray` and `ImmutableArray`. The helper functions still use the immutable version by default:
 
 ```php
 use function Tempest\Support\str;
@@ -251,7 +251,7 @@ $container->get(SerializerFactory::class)->addSerializer(Carbon::class, CarbonSe
 
 ## Vite support
 
-Enzo has worked hard to add Vite support, with the option to install Tailwind as well. It's as simple as running the Vite installer:
+{gh:innocenzi,Enzo} has worked hard to add Vite support, with the option to install Tailwind as well. It's as simple as running the Vite installer:
 
 ```php
 ~ ./tempest install vite
@@ -263,7 +263,7 @@ Next, add `{html}<x-vite-tags />`, in the `{html}<head>` of your template:
 <html lang="en" class="h-dvh flex flex-col">
   <head>
       <!-- … -->
-      
+
       <x-vite-tags/>
   </head>
   <body>
@@ -284,7 +284,7 @@ Done!
 
 ## Database improvements
 
-Vincent has simplified database configs, instead of having a single `DatabaseConfig` object with a connection, we've created a `DatabaseConfig` interface, which each driver now implements:
+{gh:blackshadev,Vincent} has simplified database configs, instead of having a single `DatabaseConfig` object with a connection, we've created a `DatabaseConfig` interface, which each driver now implements:
 
 ```php
 // app/Config/database.config.php
@@ -301,21 +301,21 @@ return new MysqlConfig(
 );
 ```
 
-Next, Matt added support for a `#[Virtual]` property, which excludes models fields from the model query:
+Next, {gh:mattdinthehouse,Matt} added support for a `#[Virtual]` property, which excludes models fields from the model query:
 
 ```php
 use Tempest\Database\Virtual;
 use Tempest\Database\DatabaseModel;
 use Tempest\Database\IsDatabaseModel;
 
 class Book implements DatabaseModel
-{   
+{
     use IsDatabaseModel;
-    
+
     // …
-    
+
     public DateTimeImmutable $publishedAt;
-    
+
     #[Virtual]
     public DateTimeImmutable $saleExpiresAt {
         get => $this->publishedAt->add(new DateInterval('P5D'));
@@ -325,7 +325,7 @@ class Book implements DatabaseModel
 
 ## New website
 
-One last thing to mention — you might have noticed it already — we've completely redesigned the Tempest website! A big shout-out to Enzo who made a huge effort to get it ready! Of course, there a lot more changes with this release, you can check the [full changelog here](https://github.com/tempestphp/tempest-framework/releases/tag/v1.0.0-alpha.6).
+One last thing to mention — you might have noticed it already — we've completely redesigned the Tempest website! A big shout-out to {gh:innocenzi,Enzo} who made a huge effort to get it ready! Of course, there a lot more changes with this release, you can check the [full changelog here](https://github.com/tempestphp/tempest-framework/releases/tag/v1.0.0-alpha.6).
 
 ## In closing