From 97a7428acf1a71409feb44efc8b4dfb14099e091 Mon Sep 17 00:00:00 2001
From: Federico Stagni <federico.stagni@cern.ch>
Date: Mon, 21 Oct 2024 12:07:10 +0200
Subject: [PATCH] remove pdfs

---
 .gitignore | 2 ++
 slides.md  | 4 ++--
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/.gitignore b/.gitignore
index c6bba59..cc478e4 100644
--- a/.gitignore
+++ b/.gitignore
@@ -10,6 +10,8 @@ lerna-debug.log*
 # Diagnostic reports (https://nodejs.org/api/report.html)
 report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json
 
+*.pdf
+
 # Runtime data
 pids
 *.pid
diff --git a/slides.md b/slides.md
index 20ad8f4..30c68c3 100644
--- a/slides.md
+++ b/slides.md
@@ -1065,7 +1065,7 @@ title: summary
       <li>We are rewriting the code, but it is still Dirac that you love!</li>
     </ul>
   </li>
-  <li>DiracX will ease the interoperability with Rucio and/or any other tool out there
+  <li>DiracX will ease the interoperability with Rucio and/or dask and/or any other tool out there
     <ul class="text-sm">
       <li>DiracX will still have the Data Management part, but its Workload Management functionalities will come first</li>
     </ul>
@@ -1194,7 +1194,7 @@ Q/A
 
 :: content ::
 
-- I am using {Rucio|AnotherTool}. I could use DiracX as WMS but do not want to fiddle with DIRAC
+- I am using {Rucio|dask|another_tool}. I could use DiracX as WMS but do not want to fiddle with DIRAC
 
 --> It will probably be possible, but we do not know when.