From 442da2b56d624fbf3260a0f86b06dcbdc2772b74 Mon Sep 17 00:00:00 2001
From: Erik Brakkee <erik@brakkee.org>
Date: Sun, 1 Sep 2024 18:16:02 +0200
Subject: [PATCH] minor update to the about page. Confusing explanation at the
 start.

---
 pkg/server/ui/about.templ | 15 ++++++++++-----
 1 file changed, 10 insertions(+), 5 deletions(-)

diff --git a/pkg/server/ui/about.templ b/pkg/server/ui/about.templ
index 23e11a4..54ac7fa 100644
--- a/pkg/server/ui/about.templ
+++ b/pkg/server/ui/about.templ
@@ -24,9 +24,18 @@ templ About() {
 
       <h2>how it works</h2>
 
+      <p>
       The basic principle of converge is described below. Access to a running remote continous integration
       job is usually not possible without a lot of access to the backend environment where jobs are running.
-      However, the job can connect to a server as well as the client. The connection between
+      However, the job can connect to a server running outside, and so can the client.
+      </p>
+
+
+      <div>
+      <img src="../static/images/converge.svg"/>
+      </div>
+
+      The connection between
       client and agent is established as follows:
       <ul>
           <li>(1): the agent, started by the continuous integration job, connects to converge server through a websocket, this establishes a connection that
@@ -46,10 +55,6 @@ templ About() {
              commands. </li>
       </ul>
 
-      <div>
-      <img src="../static/images/converge.svg"/>
-      </div>
-
       <p>There are a few special situations:
       <ul>
         <li> If no rendez-vous id is specified than a rendez-vous id is generated. </li>