clean up forking section

kercre123 · kercre123 · commit 72f093511906 · 2025-05-28T01:14:15.000-05:00
diff --git a/documents/6. Make Your Own CFW/1. prerequisites.md b/documents/6. Make Your Own CFW/1. prerequisites.md
diff --git a/documents/6. Make Your Own CFW/2. forking.md b/documents/6. Make Your Own CFW/2. forking.md
@@ -6,9 +6,9 @@ Fork wire-os and its submodules.
 
 1. Fork these repos. When choosing names, just replace the `wire-os` parts with the name you desire:
 
-- [wire-os](https://github.com/os-vector/wire-os)
-- [wire-os-victor](https://github.com/os-vector/wire-os-victor)
-- [wire-os-externals](https://github.com/os-vector/wire-os-externals)
+[wire-os](https://github.com/os-vector/wire-os)
+[wire-os-victor](https://github.com/os-vector/wire-os-victor)
+[wire-os-externals](https://github.com/os-vector/wire-os-externals)
 
 2. Let's say, for example, we called it `diode-os`, and our GitHub username is diode123. Run in a Linux terminal:
 
@@ -25,6 +25,8 @@ git rm -f anki/victor
 rm -rf anki/victor .git/modules/anki/victor
 git commit -m "remove wire-os"
 git submodule add https://github.com/diode123/diode-os-victor anki/victor
+git commit -m "new submodule"
+git push
 ```
 
-4. TODO
+- You have successfully created diodeOS.
diff --git a/documents/6. Make Your Own CFW/3. how.md b/documents/6. Make Your Own CFW/3. how.md
@@ -0,0 +1,12 @@
+# How to Develop
+
+The majority of your changes will probably be in the /anki folder, which is built from diode-os-victor.
+
+## Set up your dev environment
+
+You should have two folders: diode-os-victor and diode-os.
+
+Do NOT just make all of you changes in diode-os/anki/victor, despite it being the same repo. `diode-os-victor` can be built standalone, and deployed to a robot with `rsync`. These builds should not end up in a Yocto environment.
+
+TODO
+
