diff --git a/EliteBGS/docs/combatzone.png b/EliteBGS/docs/combatzone.png
new file mode 100644
index 0000000..eda60b0
Binary files /dev/null and b/EliteBGS/docs/combatzone.png differ
diff --git a/EliteBGS/docs/combatzones.md b/EliteBGS/docs/combatzones.md
new file mode 100644
index 0000000..6e387f2
--- /dev/null
+++ b/EliteBGS/docs/combatzones.md
@@ -0,0 +1,21 @@
+# Combat Zones
+
+Starting with version 0.2.0, the EliteBGS tool will attempt to figure out when you
+have participated in a combat zone.
+
+Since there is no official journal entry for combat zones as of yet (Update 13), the
+tool has to make an educated guess on what sort of combat zone it is.
+
+For Odyssey on foot combat zones the tool can attempt to determine the difficulty
+from the from the highest combat bond you have been awarded. Enforcers in high on foot
+combat zones nets you roughly 88k credits, and the payout reduces from there.
+
+Ship combat zones are more difficult. If you ship scan one of the warzone NPCs (either
+a captain, spec ops, or a correspondent), the tool can assume you are either in a medium
+or a high combat zone. If you get more than 10 kills, you are also either in a medium or
+high combat zone (a low combat zone is complete with 8 kills).
+
+None of this perfect however, and the tool *will* get it wrong. For your convenience there
+are several small buttons next to the combat zone entry, where you can fix the result:
+
+![combat zone](combatzone.png)
\ No newline at end of file
diff --git a/EliteBGS/mkdocs.yml b/EliteBGS/mkdocs.yml
index 15dba1b..02c7c93 100644
--- a/EliteBGS/mkdocs.yml
+++ b/EliteBGS/mkdocs.yml
@@ -10,5 +10,6 @@ theme:
 nav:
     - Overview: 'index.md'
     - "Detailed Description": 'description.md'
+    - "Combat Zones": 'combatzones.md'
     - FAQ: 'faq.md'
     - Changelog: 'CHANGELOG.md'