From 9575717c462ce6bfcadb1c21248959103a9971dd Mon Sep 17 00:00:00 2001
From: Jake Howard <git@theorangeone.net>
Date: Wed, 5 Jun 2024 11:19:54 +0100
Subject: [PATCH] Improve wording around Celery

---
 slides.md | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/slides.md b/slides.md
index b86538f..1facab3 100644
--- a/slides.md
+++ b/slides.md
@@ -754,7 +754,9 @@ class: flex justify-center text-2xl flex-col
         - If not Celery, then something else
 - That's not really the goal
     - Shared API contract is
-    - The built-in version will hopefully become great
+        - Interoperate with as opposed to replace
+        - Let you use the ecosystem which already exists
+    - The Django backends will hopefully become great
         - But must be done with careful planning and consideration
         - Django needs to remain the stable and reliable base it always has been
         - Don't want to burn-out the Django maintainers
@@ -776,7 +778,8 @@ class: flex justify-center text-xl flex-col
 - A common API
 
 <!--
-- Being built-in reduces the battier to entry
+- Why should this be built-in?
+- Being built-in reduces the barrier to entry
 - Integrating becomes much simpler
     - There's 1 API to learn
         - It will last you a while
@@ -939,9 +942,8 @@ background: /celery.svg
 <!--
 - Is this the end for Celery and alike?
     - Not at all!
-    - You've not made a mistake
-        - It's a great choice
-        - They have quite a head start
+    - It's a great choice
+    - They have quite a head start
     - This is much more about usability and flexibility
     - If you need certain features, keep using them!
 - Now you have the option of a Django-native API