diff --git a/public/md/Guess-substation-structure copy.md b/public/md/Guess-substation-structure copy.md
deleted file mode 100644
index 0686b72380..0000000000
--- a/public/md/Guess-substation-structure copy.md	
+++ /dev/null
@@ -1,26 +0,0 @@
-
-The `Substation` is an optional element and therefore is often missing in so-called bottom-up projects. With `OpenSCD` you can add the `Substation` element in the aftermath. 
-
-For exactly this purpose the `guess` function has been introduced to `OpenSCD` to either speed up this task or to give pure beginner an impression what to do. 
-
-> NOTE: A guess will never be perfect as it is based on assumptions (see below) that not necessary fit to the IEDs you have in the `SCL` file. However, you can give it a try as you can always `undo`.
- 
-This is how you can use the function:
-- Open and `SCL` file with missing substation or delete all `Substation`elements
-- Click on the fab button **+Add Substation**
-- In the dialog **Add Substation** check the box **Guess content**
-- Choose the `(ctlModel)` (**Control model**) that identify your switch gear in the IED
-- Start **GUESS CONTENT**
-
-
-> NOTE: The biggest challenge with the guess function is to identify the amount of voltage levels (`VoltageLevel`), bays (`Bay`) and so-called conducting equipment or primary equipment(`ConductingEquipment`).
-
-We therefore have to make some basic assumptions that is:
-- Assumes only one voltage level  
-- Bays are identified with the logical node `CSWI`. That means, if there is at least a logical node `CSWI` and the mandatory data object `Pos` matches the chosen control model (ctlModel) a bay is created for this particular IED.
-- Each of the logical nodes `CSWI` with matching `ctlModel ` represents a conducting equipment. If a `XCBR` is connected to it (same `prefix` and `inst` in the same `LDevice`), the conducting equipment `type` is `CBR` in every other case `DIS`. 
-- Logical node connections `LNode` are automatically assigned to the conducting equipment. Ideally this is the `CSWI`, a `XCRB` or `XSWI` and `CILO`
-
-> TIP: Especially the assumption that there is only one voltage level does not match big files with lots of IEDs. Use the **Move** function to allocate bays to other voltage levels.
-
-
diff --git a/public/md/Save-project copy.md b/public/md/Save-project copy.md
deleted file mode 100644
index 4135ba6067..0000000000
--- a/public/md/Save-project copy.md	
+++ /dev/null
@@ -1,3 +0,0 @@
-One of the things that user might be different in OpenSCD compared to a desktop application is **Save project**. As OpenSCD runs in the browser we use the browser standard behavior to save files and in most browsers this means that the file is downloaded in the download folder on your machine directly. 
-
-HOWEVER, you can change this standard behavior. In Chrome and Chromium, this setting is called **Ask where to save each file before downloading**. 
\ No newline at end of file
diff --git a/public/md/Validators copy.md b/public/md/Validators copy.md
deleted file mode 100644
index 4d01585903..0000000000
--- a/public/md/Validators copy.md	
+++ /dev/null
@@ -1,7 +0,0 @@
-Validators are the backbone of this editor. It is very tricky to handle the complexity of an SCL file without it. This is especially true for people just starting to work with SCL files and OpenSCD. In most cases, we try to avoid producing invalid files, but especially in **expert mode**, it is not always possible.
-
-There are two validation functions implemented at the moment. Both are triggered on opening an project or creating a new project. So every time the project basis change. And all validators are triggered on every editor action. That means every time there are changes in the project basis. All results are displayed in the **diagnostics** pane (Ctrl D) and are group by the validation function
-
-
-1. [Schema validator](https://github.com/openscd/open-scd/wiki/Validate-schema)
-2. [Templates validator](https://github.com/openscd/open-scd/wiki/Validate-template)
\ No newline at end of file