From f79590bf8c8f2fde4127f1fe1088352054c8121d Mon Sep 17 00:00:00 2001
From: Laura Du Ry <123562732+LauraDuRy@users.noreply.github.com>
Date: Fri, 23 Aug 2024 10:45:54 +0200
Subject: [PATCH] Update +page.markdoc

---
 src/routes/blog/post/designing-init-event-logo/+page.markdoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/routes/blog/post/designing-init-event-logo/+page.markdoc b/src/routes/blog/post/designing-init-event-logo/+page.markdoc
index b2587c9236..ddebd50cd7 100644
--- a/src/routes/blog/post/designing-init-event-logo/+page.markdoc
+++ b/src/routes/blog/post/designing-init-event-logo/+page.markdoc
@@ -10,7 +10,7 @@ category: design
 featured: false
 ---
 
-After the success of our first Init event in Spring of 2024, we knew there would be more coming soon, and that, visually, we had set ourselves a high bar. Even though Init is a fully online, virtual event, Appwrite’s visual design team created something tangible and interactive with the fully customizable, and shareable Init event tickets. In early July, knowing that our next event was just around the corner, we gathered again and began to brainstorm the visual design style that we wanted to bring to Init 2.0.
+After the success of our first [Init](https://appwrite.io/init) event in Spring of 2024, we knew there would be more coming soon, and that, visually, we had set ourselves a high bar. Even though Init is a fully online, virtual event, Appwrite’s visual design team created something tangible and interactive with the fully customizable, and shareable [Init event tickets](https://appwrite.io/init/tickets). In early July, knowing that our next event was just around the corner, we gathered again and began to brainstorm the visual design style that we wanted to bring to Init 2.0.
 
 # The Design Process