GITBOOK-33: No subject

documentation/optimizations/multithreading.md

@@ -59,7 +59,7 @@ Of course, every form of [`Query`](../query.md) is supported again. Even [**inli
     }
 }
 
-world.ParallelInlineQuery&#x3C;VelocityUpdate, Position, Velocity>(<a data-footnote-ref href="#user-content-fn-5">in queryDescription</a>); 
+world.InlineParallelQuery&#x3C;VelocityUpdate, Position, Velocity>(<a data-footnote-ref href="#user-content-fn-5">in queryDescription</a>); 
 </code></pre>
 
 {% hint style="warning" %}
@@ -86,7 +86,7 @@ If this is all too high level for you, there is also the option of tackling the
    }
 }
 
-world.ParallelQuery(in query, <a data-footnote-ref href="#user-content-fn-6">new VelocityUpdate()</a>);
+world.InlineParallelChunkQuery(in query, <a data-footnote-ref href="#user-content-fn-6">new VelocityUpdate()</a>);
 </code></pre>
 
 {% hint style="info" %}

extensions/page-3/arch.system.sourcegenerator.md

@@ -6,3 +6,14 @@ description: >-
 
 # Arch.System.SourceGenerator
 
+I know, I know... writing queries is always sooo much work. If only you could have it all generated... wait... you can!
+
+The `Arch.System.SourceGenerator` package provides some code generation utils. With them, queries can be written virtually by themselves which saves some boilerplate code.
+
+**Query** methods can be generated **in** [**all classes**](#user-content-fn-1)[^1] **as long as they are partial**. However it makes most sense in the [`BaseSystem`](arch.system.md). The attributes can be used to meaningfully describe what query to generate, and the query will always call the annotated method.
+
+## Start the engine
+
+
+
+[^1]: Also static ones, without a `BaseSystem` inheritance.