Update concept.md

Author: oblomov-dev

docs/advanced/technical/concept.md

@@ -23,11 +23,11 @@ This results in a clean and lightweight frontend — a pure rendering layer —
 _HTML "Over the Wire" Lifecycle [(2)](https://community.sap.com/t5/technology-blog-posts-by-members/fiori-like-web-app-development-in-pure-abap-with-htmx-and-fundamental/ba-p/13500763)_
 
 Several modern frameworks follow this pattern:
-* [htmx](https://htmx.org), Progressive enhancement via HTML partials, Any web stack
-* [Hotwire (Turbo)](https://hotwired.dev), HTML-over-the-wire for Rails apps, Ruby on Rails
-* [Phoenix LiveView](https://hexdocs.pm/phoenix_live_view), Real-time UI with server rendering,, Elixir / Phoenix
-* [Livewire](https://livewire.laravel.com), Server-driven UI components in PHP, Laravel / PHP
-* [Unpoly](https://unpoly.com), Simplified partial page updates, Any web stack
+* [htmx](https://htmx.org) Progressive enhancement via HTML partials (Any web stack)
+* [Hotwire (Turbo)](https://hotwired.dev) HTML-over-the-wire for Rails apps (Ruby on Rails)
+* [Phoenix LiveView](https://hexdocs.pm/phoenix_live_view) Real-time UI with server rendering (Elixir/Phoenix)
+* [Livewire](https://livewire.laravel.com) Server-driven UI components in PHP  (Laravel/PHP)
+* [Unpoly](https://unpoly.com) Simplified partial page updates (Any web stack)
 
 
 #### But isn't this just old-school server rendering?