Alignment adjustments

Author: davedbase

src/pages/Articles/solid-start-the-shape-frameworks-to-come.mdx

@@ -22,7 +22,10 @@ SolidStart’s base does not lock you into any specific conventions. Adopting so
 
 SolidStart does have Filesystem routing. It uses similar conventions to Nuxt where parameters are passed via `[]`. However, we also use `()` as a way to do more powerful things like Route Groups, named index routes, and as a way to break out of nesting. Basically whatever you put between the parenthesis is removed from matching, but still impacts the structure of your routes.
 
-![Image description](/img/blog/solid-start-the-shape-frameworks-to-come/routes-tree.png)
+<center>
+  ![A screenshot of route
+  structure](/img/blog/solid-start-the-shape-frameworks-to-come/routes-tree.png)
+</center>
 
 The configuration that we get from the File System is then passed back to the application to be used in the router of your choice. You can call FileRoutes as a component or a regular function to get the configuration generated by SolidStart.
 
@@ -97,7 +100,10 @@ Our server functions support advanced serialization for this like Async Iterable
 
 We've used this capability to do things like Single Flight Mutations with Solid Router's API which lets the server start fetching the data for the next page after an update and stream it back on the same response while the client handles the redirect. Between this, parallelized load/cache patterns, and Solid's non-blocking Async, we've all but eliminated unnecessary waterfalls.
 
-![Image description](/img/blog/solid-start-the-shape-frameworks-to-come/single-flight.png)
+<center>
+  ![A chart demonstrating single-flight
+  mutations](/img/blog/solid-start-the-shape-frameworks-to-come/single-flight.png)
+</center>
 
 You can see this in our [Notes example](https://github.com/solidjs/solid-start/tree/main/examples/notes).
 
@@ -107,6 +113,6 @@ Honestly, there are too many features to talk about with SolidStart because your
 
 This is a framework designed for builders and people who have their own opinions. We're only beginning to tap into the potential here. That's what we mean by "The Shape of Frameworks to Come". SolidStart won't be the last Solid Framework. We're just getting started. We've already seen people build Meta-Frameworks on top of it like CreateJDApp and MediaKit.
 
-And for that, we (the Solid Core Team) are incredibly thankful. Thankful for all the contributors submitting issues and PRs. Thankful for open-source projects that make this technically possible like Vite, Vinxi, and Nitro. Thankful for all the sponsors contributing funding like Netlify, Google Chrome, and JetBrains. But most importantly we're thankful to all of you for embracing development in the open, choosing better over convenient, and sticking with us on this journey. You inspire us to keep building the best solutions we can and to continue to shape the future of web development.
+And for that, we (the Solid Core Team) are incredibly thankful. Thankful for all the contributors submitting issues and PRs. Thankful for open-source projects that make this technically possible like Vite, Vinxi, and Nitro. Thankful for all the sponsors contributing funding like Netlify, Google Chrome, and JetBrains. Most importantly we're thankful to all of you for embracing development in the open, choosing better over convenient, and sticking with us on this journey. You inspire us to keep building the best solutions we can and to continue to shape the future of web development.
 
 <YouTube youTubeId="ZVjXtfdKQ3g" />