fixes

slides.md

@@ -268,8 +268,7 @@ DMS[("`**Data
 Management
 System**`")]
 style DMS fill:#bbf
-FC[["`**Files
-Catalog**`"]]
+FC[["`**Catalog**`"]]
 style FC fill:#bbf
 StorageBase[["`**Storage Base**`"]]
 style StorageBase fill:#bbf
@@ -297,6 +296,10 @@ StorageBase-->WebDav
 StorageBase-->XRootD
 ```
 
+<!-- 
+A catalog is effectively an interface, that needs implementation. Such implementation can be the DIRAC Files Catalog, or Rucio, or any other, including extension specific ones
+-->
+
 
 ---
 layout: side-title
@@ -378,7 +381,7 @@ Dashboards can be created within the DIRAC Web App:
 
 and/or in Grafana:
 
-<img src="/public/images/running_jobs_90.png" alt="DIRAC_stack" class="mx-auto w-2/3"/>
+<img src="/public/images/running_jobs_90.png" alt="DIRAC_stack" class="mx-auto w-4/5"/>
 
 
 ---
@@ -391,7 +394,7 @@ title: DIRAC tech
 
 :: title ::
 
-# DIRAC Tech stack 
+# Technicalities
 
 :: content :: 
 
@@ -406,9 +409,14 @@ title: DIRAC tech
       <li><code>dips</code> stands for "DIRAC protocol"</li>
     </ul>
   </li>
-  <li>The DIRAC framework provides also "Agents" (~ cron jobs) and "Executors" (~  ) to animate the system</li>
+  <li>The DIRAC framework provides also "Agents" (~ cron jobs) and "Executors" (~ tasks execution) to animate the system</li>
   <li>As backends, <logos-mysql class="text-2xl align-middle inline-block mx-0"></logos-mysql> and <logos:opensearch class="text-1xl align-middle inline-block mx-0"></logos:opensearch> are supported (for different purposes)</li>
-  <li>The Web App is implemented using `ExtJS`, and fully custom Python "bindings"</li>
+  <li>The Web App is implemented using <code>ExtJS</code>, and fully custom Python "bindings"</li>
+  <li>For AuthN/Z, DIRAC understands certificates and proxies
+    <ul class="text-xs">
+      <li>VOMS (Virtual Organization Membership Service) is effectively a hard DIRAC dependency</li>
+    </ul>
+  </li>
 </ul>