From 37d93736d8847faa442309c956b7f501089a7d28 Mon Sep 17 00:00:00 2001
From: Mariska <40423138+MariMakes@users.noreply.github.com>
Date: Mon, 18 Mar 2024 13:30:18 +0100
Subject: [PATCH] Updated Call to Action to 5.7 Beta

We are now sending our users  from the Nightly to the 5.7 Beta with several improvements and the updated slicing analysis tool
---
 .github/ISSUE_TEMPLATE/SlicingCrash.yaml | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/SlicingCrash.yaml b/.github/ISSUE_TEMPLATE/SlicingCrash.yaml
index f4e082e00a..0d93977627 100644
--- a/.github/ISSUE_TEMPLATE/SlicingCrash.yaml
+++ b/.github/ISSUE_TEMPLATE/SlicingCrash.yaml
@@ -5,11 +5,10 @@ body:
 - type: markdown
   attributes:
     value: |      
-       ### 💥 Slicing Crash Analysis Tool 💥
-       We are taking steps to analyze an increase in reported crashes more systematically. We'll need some help with that. 😇
-       Before filling out the report below, we want you to try a special Cura 5.7 Alpha.
-       This version of Cura has an updated slicing engine that will automatically send a report to the Cura Team for analysis. 
-       #### [You can find the downloads here](https://github.com/Ultimaker/Cura/discussions/18080) #### 
+       ### ✨Try our improved Cura 5.7✨
+       Before filling out the report below, we want you to try the latest Cura 5.7 Beta. 
+       This version of Cura has become significantly more reliable and has an updated slicing engine that will automatically send a report to the Cura Team for analysis. 
+       #### [You can find the downloads here](https://github.com/Ultimaker/Cura/releases/tag/5.7.0-beta.1) #### 
        If you still encounter a crash you are still welcome to report the issue so we can use your model as a test case, you can find instructions on how to do that below.      
        
        ### Project File