diff --git a/reference/parallel/parallel.events.input.xml b/reference/parallel/parallel.events.input.xml
index bd5acb9208..e4a52d636e 100644
--- a/reference/parallel/parallel.events.input.xml
+++ b/reference/parallel/parallel.events.input.xml
@@ -8,6 +8,21 @@
 
  <partintro>
 
+  <section>
+    <title>Events Input</title>
+    <para>
+     An Input object is a container for data that the <classname>parallel\Events</classname> object will write to 
+     <classname>parallel\Channel</classname> objects as they become available. Multiple event loops may share an Input container - parallel does not 
+     verify the contents of the container when it is set as the input for a <classname>parallel\Events</classname> object.
+    </para>
+    <note>
+    <para>
+     When a <classname>parallel\Events</classname> object performs a write, the target is removed from the input object as if 
+     <methodname>parallel\Events\Input::remove</methodname> were called.
+    </para>
+    </note>
+  </section>
+
   <section xml:id="parallel-events-input.synopsis">
    &reftitle.classsynopsis;
 
diff --git a/reference/parallel/parallel.runtime.xml b/reference/parallel/parallel.runtime.xml
index 7ca8afc26f..3464e7b5ec 100644
--- a/reference/parallel/parallel.runtime.xml
+++ b/reference/parallel/parallel.runtime.xml
@@ -8,6 +8,36 @@
 
  <partintro>
 
+  <section>
+    <title>Runtime Objects</title>
+    <para>
+     Each runtime represents a single PHP thread, the thread is created (and bootstrapped) upon construction. 
+     The thread then waits for tasks to be scheduled: Scheduled tasks will be executed FIFO and then the thread will resume waiting until 
+     more tasks are scheduled, or it's closed, killed, or destroyed by the normal scoping rules of PHP objects.
+    </para>
+    <warning>
+     <para>
+      When a runtime is destroyed by the normal scoping rules of PHP objects, it will first execute all of the tasks that were scheduled,
+      and block while doing so. 
+     </para>
+    </warning>
+  </section>
+
+  <section>
+    <title>Runtime Bootstrapping</title>
+    <para>
+     When a new runtime is created, it does not share code with the thread (or process) that created it. This means it doesn't have the same
+     classes and functions loaded, nor the same autoloader set. In some cases, a very lightweight runtime is desirable because the tasks that
+     will be scheduled do not need access to the code in the parent thread. In those cases where the tasks do need to access the same code, it
+     is enough to set an autoloader as the bootstrap.
+    </para>
+    <note>
+     <para>
+      preloading may be used in conjunction with parallel, in this case preloaded code is available without bootstrapping
+     </para>
+    </note>
+  </section>
+
   <section xml:id="parallel-runtime.synopsis">
    &reftitle.classsynopsis;