maxitg · maxitg · Jul 19, 2021 · Jun 16, 2021 · Jun 17, 2021 · Jul 7, 2021
diff --git a/Documentation/Generators/$SetReplaceGenerators.md b/Documentation/Generators/$SetReplaceGenerators.md
@@ -0,0 +1,9 @@
+# $SetReplaceGenerators
+
+**`$SetReplaceGenerators`** gives the list of all generators that can be used to evaluate
+[computational systems](/Documentation/Systems/README.md):
+
+```wl
+In[] := $SetReplaceGenerators
+Out[] = {GenerateMultihistory, GenerateSingleHistory}
+```
diff --git a/Documentation/Generators/$SetReplaceSystems.md b/Documentation/Generators/$SetReplaceSystems.md
@@ -1,7 +1,7 @@
 # $SetReplaceSystems
 
 **`$SetReplaceSystems`** gives the list of all [computational systems](/Documentation/Systems/README.md) that can be
-used with [GenerateMultihistory](/Documentation/Generators/GenerateMultihistory.md) and related functions:
+used with [GenerateMultihistory](/Documentation/Generators/GenerateMultihistory.md) and other [generators](README.md):
 
 ```wl
 In[] := $SetReplaceSystems

diff --git a/Documentation/Generators/EventOrderingFunctions.md b/Documentation/Generators/EventOrderingFunctions.md
diff --git a/Documentation/Generators/EventSelectionParameters.md b/Documentation/Generators/EventSelectionParameters.md
diff --git a/Documentation/Generators/GenerateMultihistory.md b/Documentation/Generators/GenerateMultihistory.md
@@ -1,24 +1,15 @@
 # GenerateMultihistory
 
-**`GenerateMultihistory`** is the most verbose and configurable generator. It can create both single histories, full
-multihistories, as well as partial ones. It, however, requires one to specify all groups of parameters
-([system](/Documentation/Systems/README.md), [event selection](EventSelectionParameters.md), deduplication,
-[event ordering](EventOrderingFunctions.md) and [stopping conditions](StoppingConditionParameters.md)), nothing is
-implied automatically:
-
-```wl
-GenerateMultihistory[
-  system, eventSelectionSpec, tokenDeduplicationSpec, eventOrderingSpec, stoppingConditionSpec] @ init
-```
+**`GenerateMultihistory`** is the most configurable multihistory generator. With no parameters specified, it attempts to
+generate all possible histories starting from the initial state. However, it can be configured to generate partial
+multihistories and even single histories, although [`GenerateSingleHistory`](GenerateSingleHistory.md) is more
+convenient for that.
 
 For example, for a [`MultisetSubstitutionSystem`](/Documentation/Systems/MultisetSubstitutionSystem.md):
 
 ```wl
-In[] := multihistory = GenerateMultihistory[MultisetSubstitutionSystem[{a_, b_} :> {a + b}],
-                                            {"MaxDestroyerEvents" -> 3},
-                                            None,
-                                            EventOrderingFunctions[MultisetSubstitutionSystem],
-                                            {"MaxEvents" -> 10}] @ {1, 2, 3, 4}
+In[] := multihistory = GenerateMultihistory[
+  MultisetSubstitutionSystem[{a_, b_} :> {a + b}], MaxDestroyerEvents -> 3, MaxEvents -> 10] @ {1, 2, 3, 4}
 ```
 
 <img src="/Documentation/Images/MultisetMultihistory.png" width="472.2">
@@ -29,11 +20,3 @@ In[] := #["ExpressionsEventsGraph", VertexLabels -> Placed[Automatic, After]] &
 ```
 
 <img src="/Documentation/Images/GenerateMultihistoryExample.png" width="478.2">
-
-Everything that can be generated with more specialized `GenerateSingleHistory` and `GenerateFullMultihistory` can be
-reproduced with `GenerateMultihistory` as well. This can be done by setting `"MaxDestroyerEvents" -> 1` to emulate
-`GenerateSingleHistory` and setting `"MaxDestroyerEvents" -> Infinity` and leaving the
-[stopping condition](StoppingConditionParameters.md) empty to emulate `GenerateFullMultihistory`.
-
-However, by setting `"MaxDestroyerEvents"` to finite values larger than 1, one can generate multihistories not possible
-with other generators.