diff --git a/new-todo.md b/new-todo.md
deleted file mode 100644
index 77cc563..0000000
--- a/new-todo.md
+++ /dev/null
@@ -1,14 +0,0 @@
-# DO NOT TOUCH THIS; ONLY HUMANS ARE ALLOWED IN THIS FILE
-
-## High prio
-
-- If we have vacation days that are in risk of being lost, then the planner should run to update the kind of days used in the plan to use more vacation days (thus saving PL days).
-
-- On every event that updates the days off (i.e. the calendar is making some changes), that should trigger the planner to recalculate the best kinds of time-off for all days. 
-
-## medium prio
-- Update all deprecated things in the backend code.
-
-## lowest prio
-
-- check if the security audit findings have been done
\ No newline at end of file
diff --git a/nextTodo.md b/nextTodo.md
deleted file mode 100644
index e6c2fa2..0000000
--- a/nextTodo.md
+++ /dev/null
@@ -1,19 +0,0 @@
-- Check how the "Förskolans planeringsdagar per år" is used: Automatically just removed from the count?
-    - This should be a per year "how many did you take" so that we also know the true number each year
-    to better understand how many days might go lost.
-    - This also needs to be displayed better in the overview.
-
-- Clicking the Ledig/Arbetsdag in the list of all red days makes the page reload and the user is scrolled to the top. Not nice UX. Instead should not scroll and the blob should simply switch once this is updated in the backend. Also, the list of "undantag" should auto-update because this is a react frontend which can update only the parts that need to do so when the data updates. The data should become stale since we do an action (flip between working and non-working) and then it should auto-refetch and thus update the UI.
-
-- How does it work when the other parent wants to login? beacuse that parent should be connected to the same
-plan and same child. This whole user flow needs to be looked over.
-
-- Inputting the number of vacation days is now only possible for the logged in parent, but not possible
-to change the other parent (if available). This should be done since we are able to change the other parent's
-PL days, so should the vacation days be possible to change
-
-- Updating the amount of vacation days now leads to needing to click save for each year in the settings, that 
-is super annoying. (And an issue we have already talked about). The way to do it is with a debounce and autosave
-WITHOUT reloading the entire page.
-
-- I don't understand the vacation calculations right now, it doesn't give me confidence: For Jacob it says that he has 30 days, 15 are planned so thus 15 are left. Then it says that only 10 are saved for next year (which is correct since I can only save what is over 20), but it says that 0 are expiring! This is super important to warn/highlight, so that Jacob takes out more vacation. And maybe that the planner should make sure to say that we should switch out PLs (if possible) to vacation to not expire any days. This would lead to more PL days, which can lead to the ability to be on time off longer in the future. Image that shows how it currently looks like here: ![](./vacation_issues.png)
\ No newline at end of file
diff --git a/todo.md b/todo.md
index 062adec..280282c 100644
--- a/todo.md
+++ b/todo.md
@@ -9,4 +9,22 @@ Following three have a plan (worked on the plan):
 
   - If we have vacation days that are in risk of being lost, then the planner should run to update the kind of days used in the plan to use more vacation days (thus saving PL days).
 
-  - On every event that updates the days off (i.e. the calendar is making some changes), that should trigger the planner to recalculate the best kinds of time-off for all days. 
\ No newline at end of file
+  - On every event that updates the days off (i.e. the calendar is making some changes), that should trigger the planner to recalculate the best kinds of time-off for all days. 
+
+## Below here is taken from another markdown file, so should probaby be filtered and removed
+## High prio
+
+- If we have vacation days that are in risk of being lost, then the planner should run to update the kind of days used in the plan to use more vacation days (thus saving PL days).
+-> have a plan I think
+
+- On every event that updates the days off (i.e. the calendar is making some changes), that should trigger the planner to recalculate the best kinds of time-off for all days. 
+-> have a plan I think
+
+## medium prio
+- Update all deprecated things in the backend code.
+-> Plan creation in progress
+
+## lowest prio
+
+- check if the security audit findings have been done
+-> yet to have a plan
\ No newline at end of file
diff --git a/vacation_issues.png b/vacation_issues.png
deleted file mode 100644
index a088a69..0000000
Binary files a/vacation_issues.png and /dev/null differ