diff --git a/slides/datastar/slides.md b/slides/datastar/slides.md
index 2c9477b..3df07d3 100644
--- a/slides/datastar/slides.md
+++ b/slides/datastar/slides.md
@@ -3,7 +3,7 @@
 theme: default
 # random image from a curated Unsplash collection by Anthony
 # like them? see https://unsplash.com/collections/94734566/slidev
-background: assets/galaxy.jpg
+background: /galaxy.jpg
 # some information about your slides (markdown enabled)
 title: Datastar
 # apply UnoCSS classes to the current slide
@@ -28,7 +28,7 @@ The last comment block of each slide will be treated as slide notes. It will be
 -->
 
 ---
-background: assets/galaxy.jpg
+background: /galaxy.jpg
 ---
 
 
@@ -123,7 +123,7 @@ transition: fade-out
 
 ### Finding my combination of web technologies for a minimal viable web application.
 
-<div class="mt-10"/>  v
+<div class="mt-10"/>
 
 - Part 1: The Database: SQLite
 - Part 2: The No-ORM ORM - A very simple Data Abstraction Layer.
@@ -144,8 +144,6 @@ transition: fade-out
 
 ## It is not SQ-Lite, it is SQL-ite
 
-
-
 Since everybody knows SQLite, today just a few highlights:
 
 - It has JSON and JSONB as built-in data types.
@@ -153,7 +151,8 @@ Since everybody knows SQLite, today just a few highlights:
 - It's CTEs make SQL Turing complete.
 - The SQLite CLI can be used to execute "SQL-scripts". See demo.
 
-\* It lacks features essential for a client-server environment, primarily multi-user concurrent write access, built-in security and user management, and some advanced data types.
+\* It lacks features essential for a client-server environment, primarily multi-user concurrent write access, 
+built-in security and user management, and some advanced data types.
 
 <div class="mt-40"/>
 
@@ -215,17 +214,6 @@ Quote Gillian Delany: 
 
 
 
----
-class: default
----
-
-# Term-Soup:
-<div class="mt-10"/>
-
-ADR, core+plugins, Signals, Ideomorph, Core-Engine, Plug-ins, SSE, 
-You have to control the backend, Templating, HTMX, Hypermedia, Hateoas, 
-Locality of behaviour, 
-Declarative vs. Imperative, DS conforms strictly to the web's specs.
 ---
 class: default
 ---
@@ -363,6 +351,20 @@ sequenceDiagram
     Backend-->>Browser: event: updatedata: {...}
     Note over Browser,Backend: Real-time updates without new requests
 ```
+---
+layout: default
+transition: fade-out
+---
+
+# Hypermedia
+
+- The Representation is the Data: The representation (e.g., the HTML document) delivered from the server to the client contains all the data needed for that specific application state.
+
+- Presentation and Links are Embedded: Crucially, not only is the raw data embedded, but also the presentation instructions (via CSS or HTML structure) and, most importantly for the workflow, the hypermedia controls (links and forms) that define the next possible state transitions.
+
+- Hypermedia as the Engine of Application State (HATEOAS): This is the central feature of the workflow. The representations sent from the server must include hyperlinks and/or forms that indicate the valid next state transitions (the available actions) the client can take. The client does not use pre-compiled knowledge of the workflow; it is driven by the links provided in the current document.
+
+
 ---
 layout: two-cols
 layoutClass: gap-2
@@ -445,7 +447,7 @@ class: default
 
 ---
 layout: image
-image: assets/mariner.png
+image: /mariner.png
 transition: slide-up
 level: 2
 ---