diff --git a/events/AusCERT2024_Enhancing_Cybersecurity_Collaboration/content/IntroductionToMISPandISACs_content.tex b/events/AusCERT2024_Enhancing_Cybersecurity_Collaboration/content/IntroductionToMISPandISACs_content.tex
index 690e9ff..616c23e 100644
--- a/events/AusCERT2024_Enhancing_Cybersecurity_Collaboration/content/IntroductionToMISPandISACs_content.tex
+++ b/events/AusCERT2024_Enhancing_Cybersecurity_Collaboration/content/IntroductionToMISPandISACs_content.tex
@@ -142,7 +142,6 @@
 \begin{frame}
 	\frametitle{Bringing different sharing communities together}
 	\begin{itemize}
-		\item Getting your community to be active takes \textbf{time and effort}, but with persistence your chances are great
 		\item We generally all \textbf{end up sharing with peers that face similar threats}
 		\item Division is either \textbf{sectorial or geographical}
 		\item So why even bother with trying to bridge these communities?
diff --git a/events/AusCERT2024_Enhancing_Cybersecurity_Collaboration/slides/Introduction_to_MISP_and_ISACs.pdf b/events/AusCERT2024_Enhancing_Cybersecurity_Collaboration/slides/Introduction_to_MISP_and_ISACs.pdf
index e121792..ebb0de6 100644
Binary files a/events/AusCERT2024_Enhancing_Cybersecurity_Collaboration/slides/Introduction_to_MISP_and_ISACs.pdf and b/events/AusCERT2024_Enhancing_Cybersecurity_Collaboration/slides/Introduction_to_MISP_and_ISACs.pdf differ