diff --git a/.docs/web/pages/advanced/lanes.html b/.docs/web/pages/advanced/lanes.html
index 19be447..6303f44 100644
--- a/.docs/web/pages/advanced/lanes.html
+++ b/.docs/web/pages/advanced/lanes.html
@@ -57,7 +57,7 @@
                     Another term that we have used in the code is `Chapter` which refers to a grouping of mission stages within a lane. <br>
                     These are implied and cannot be directly controlled or altered. <br>
                     A chapter is a set of `MissionStage`s that are directly connected. <br>
-                    For `MissionStages` `[ A1, A2, A3, A5, A6]` there are 2 chapters: `[ A1, A2, A3]` and `[ A5, A6]`. <br>
+                    For <code-inline>MissionStages</code-inline> <code-inline>[ A1, A2, A3, A5, A6 ]</code-inline> there are 2 chapters: <code-inline>[ A1, A2, A3 ]</code-inline> and <code-inline>[ A5, A6 ]</code-inline>. <br>
                     Within a chapter the stages are only directly dependent on each other. Meaning A2 will start when A1 is completed. <br>
                     <br>
                     However, the chapter start is where the inter-lane dependencies come into play. <br>
@@ -66,7 +66,6 @@
                     In the Visual example you can see the Stages grouped into chapters by the red boxes. <br>
 
                     <h4>Side Lane Chapter start</h4>
-
                     <p>
                         Side lane chapters are started when all are true: 
                         <ul>
@@ -111,7 +110,10 @@
                     Due to the CAP naming conventions, we've opted to currently have CAP only react with the main lane. <br>
                     This might mean a bit less flexibility when using lanes for major mission logic, however, it's a limitation we've accepted for now. <br>
                     In the future we might be able to extend CAP's interaction with other lanes as well. <br>
-                    Currently <a href="https://git.dutchie031.com/Spearhead/spearhead/issues/47">this issue</a> can be tracked here.
+                    Currently <a href="https://git.dutchie031.com/Spearhead/spearhead/issues/47">this issue</a> can be tracked here. <br>
+
+                    This does not mean having both CAP and side-lanes is out of the question, since you can still have that side-lanes scouted by CAP aircraft.
+                    It just needs a bit more pre-planning on where and how those CAP flights fly. <br>
                 </p>
             </div>
         </div>
diff --git a/RELEASENOTES.md b/RELEASENOTES.md
index 5e31f9c..f50f92b 100644
--- a/RELEASENOTES.md
+++ b/RELEASENOTES.md
@@ -5,7 +5,9 @@
 
 ### New Features
 
-- Issue 
+- Issue: #41
+  Adds Stage Complete debug methods for local testing of the Stage flow.
+  #40
 
 - Issue: #35
   Creating Lane option for stages.