diff --git a/cadence_language_and_execution_working_group/README.md b/cadence_language_and_execution_working_group/README.md
index b0b2b66..c13eb71 100644
--- a/cadence_language_and_execution_working_group/README.md
+++ b/cadence_language_and_execution_working_group/README.md
@@ -16,23 +16,6 @@ In the Early 2024 the purpose of the working group was expanded to also cover to
 * [How To Engage With The Cadence Working Group](#How-To-Engage-With-The-Cadence-Working-Group)
 * [Minutes/Recordings](#minutes)
 
-### Current Priorities
-
-- Complete & Launch Cadence 1.0 Release (Covered by milestones 1-6 in the roadmap table below).
-
-## Roadmap
-
-| Features / Milestones | Status | Release Target | Progress     | Comments |
-| ---------------------------------------------------| --------- |---------|--------------| ------------- |
-| 1: [Complete Cadence 1.0 Implementation](https://github.com/onflow/cadence/issues/2642) | In Progress | 30 March 2024 | On Track     |All Must-have Features and breaking changes have been completed. Remaining scope covers mainly bugs and small improvements. [Learn more about Cadence 1.0 changes](https://forum.flow.com/t/update-on-cadence-1-0/5197).|
-| 2: Complete [EVM on Flow Implementation](https://github.com/onflow/flow-go/issues/5241) | In Progress | Feb 2024 |              | |
-| 3: Complete [EVM JSON RPC Endpoint Implementation](https://github.com/onflow/flow-evm-gateway/issues/12) | In Progress | Feb 2024 |              | |
-| 4: Complete Cadence 1.0 State Migrations Implementation | In Progress | End of Jan 2024 |              | |
-| 5: Launch Cadence 1.0 and Flow EVM on [Crescendo Stable TestNet](https://forum.flow.com/t/update-on-cadence-1-0-upgrade-plan/5597) | In Progress | Feb 2024 |              |Learn more about the launch plan [here](https://forum.flow.com/t/cadence-1-0-upgrade-plan/5477) |
-| 6: Launch Cadence 1.0 on [Crescendo Migration TestNet](https://forum.flow.com/t/update-on-cadence-1-0-upgrade-plan/5597) | Not Started | Feb 2024 |              | Learn more about the launch plan [here](https://forum.flow.com/t/cadence-1-0-upgrade-plan/5477)|
-|Design & develop capabilities for backward-compatible language evolution and non-breaking language extensions.| On Hold | TBD     |              | On hold until we have capacity. One area of focus is for example Cadence compilation and runtime bytecode execution in the Cadence VM.|
-| Start work on Cadence language specification | Not Started | Q2 2024 |              |This goal will have multiple phases, moving from informal to formal specification definition and will span range of short and long-term priorities. It delivers incremental benefits as it progresses, in 2 core areas; efficiency of implementing new features and hardening the implementation. More specifically, it will enable efficient validation of the Cadence codebase against the specification and enforce more structured audit of the implementation as the specification is written. It will also make it more efficient to write defensive checks (e.g. resource duplication) and alternative components like compiler. In other words - instead of relying on deriving the correct behaviour from the current implementation, we will be able to derive it from specification, which is much easier.|
-
 
 ## How To Engage With The Cadence Language and Execution Working Group
 
@@ -48,3 +31,9 @@ Anyone can request a topic being added to the meeting agenda by contacting the [
 
 ## Minutes
 Minutes & Recordings from previous meetings will be made available here in github.
+
+### Current Priorities
+
+[Cadence Language goals - Q4 2024](https://github.com/onflow/cadence/issues/3623)
+
+