Removed adding from migration, adding other section blocks

Projects/Superalgos/Schemas/Docs-Nodes/actual-rate.json

@@ -13,14 +13,6 @@
         {
             "style": "Text",
             "text": "The system uses the actual rate to update the calculation of balances, which are otherwise calculated with the original rate, by default."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Actual Rate"
-        },
-        {
-            "style": "Text",
-            "text": "To add the actual rate node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/algorithm-name.json

@@ -9,14 +9,6 @@
         {
             "style": "Text",
             "text": "Assigning names to execution algorithms in the definition of the trading system makes tracking the execution of orders easier."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Algorithm Name"
-        },
-        {
-            "style": "Text",
-            "text": "To add the algorithm name node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/annualized-rate-of-return.json

@@ -221,14 +221,6 @@
         {
             "style": "Text",
             "text": "        ) - 1"
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Annualized Rate Of Return"
-        },
-        {
-            "style": "Text",
-            "text": "To add the annualized rate of return node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/asset.json

@@ -3,20 +3,8 @@
     "definition": "An asset node is the definition of an asset listed at the corresponding exchange.",
     "paragraphs": [
         {
-            "style": "Title",
-            "text": "Adding a Asset"
-        },
-        {
-            "style": "Text",
-            "text": "To add an asset, select Add Asset on the exchange assets node menu."
-        },
-        {
-            "style": "Text",
-            "text": "To add assets in bulk, select Add Missing Assets on the exchange assets node menu. Beware that the exchange may handle hundreds of assets. Before using this option you may want to implement a filter using the exchange assets configuration."
-        },
-        {
-            "style": "Text",
-            "text": "{% include /crypto_ecosystem/exchange-assets.md heading=\"\" icon=\"no\" adding=\"\" configuring=\"#####\" starting=\"\" content=\"no\" definition=\"no\" table=\"\" more=\"yes\"%}"
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/backtesting-session.json

@@ -11,16 +11,8 @@
             "text": "A backtesting session node must reference a trading system to gain access to the trading logic to be applied during the session. Other considerations framing the session come from the set of parameters attached to it."
         },
         {
-            "style": "Title",
-            "text": "Adding a Backtesting Session"
-        },
-        {
-            "style": "Text",
-            "text": "To add a backtesting session, select Add Backtesting Session on the trading process instance node menu. When a session is added, it is created with the full set of parameters."
-        },
-        {
-            "style": "Note",
-            "text": "After adding a session node, make sure you establish a reference to the trading system you want it to work with."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",
@@ -46,6 +38,10 @@
             "style": "List",
             "text": "folderName allows you to set a significant name to the folder in which the data products—and logs—generated by the session are stored. If left blank, the system names the folders with the session id. This may be handy when you intend to consult the raw data generated by the session, as, otherwise, the folder would be hard to identify."
         },
+        {
+            "style": "Block",
+            "text": "Running"
+        },
         {
             "style": "Title",
             "text": "Running Backtesting Session"

Projects/Superalgos/Schemas/Docs-Nodes/balance.json

@@ -9,14 +9,6 @@
         {
             "style": "Text",
             "text": "The balance of an asset changes every time an order involving the asset is filled. When the trading bot consults the exchange to find out the status of each order placed, the exchange answers with the size filled and actual rate for the order. That is the information used to calculate balances."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Balance"
-        },
-        {
-            "style": "Text",
-            "text": "To add the balance node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/begin-balance.json

@@ -13,14 +13,6 @@
         {
             "style": "Text",
             "text": "In the context of a position, it is the balance at the datetime the position started."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Begin Balance"
-        },
-        {
-            "style": "Text",
-            "text": "To add the begin balance node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/begin-rate.json

@@ -17,14 +17,6 @@
         {
             "style": "Text",
             "text": "In the context of an episode, it is the close rate of the last closed candle at the moment the episode starts."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Begin Rate"
-        },
-        {
-            "style": "Text",
-            "text": "To add the begin rate node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/begin.json

@@ -9,14 +9,6 @@
         {
             "style": "Text",
             "text": "In the context of a candle, it is the datetime of the open of the candle as provided by the exchange."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Begin"
-        },
-        {
-            "style": "Text",
-            "text": "To add the begin node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/bot-data-dependencies.json

@@ -11,20 +11,8 @@
             "text": "The device exists as an offspring of a data mine data dependencies node, and does not require a reference to a bot in the given data mine."
         },
         {
-            "style": "Title",
-            "text": "Adding a Bot Data Dependencies"
-        },
-        {
-            "style": "Text",
-            "text": "To add the bot data dependencies node, select Add Bot Data Dependencies on the parent node menu. When adding a bot data dependency in this manner, the node does not inherit any particular label. In fact, it may even host data dependencies pointing to other data mines."
-        },
-        {
-            "style": "Text",
-            "text": "The bot data dependencies node may also be created automatically. When created using the Add All Data Dependencies option on the data mine data dependencies node, the node inherits the label of the corresponding bot in the corresponding data mine."
-        },
-        {
-            "style": "Note",
-            "text": "See the data dependency node definition and the Adding a Data Dependecy Node section for all the details."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/bot-products.json

@@ -15,20 +15,8 @@
             "text": "The use of the bot products node is optional, as data products may also exist outside of bot products."
         },
         {
-            "style": "Title",
-            "text": "Adding a Bot Products"
-        },
-        {
-            "style": "Text",
-            "text": "To add a bot products node, select Add Bot Products on the parent node menu."
-        },
-        {
-            "style": "Text",
-            "text": "The bot products node may also be created automatically. When created using the Add All Data Products option on the data mine products node, the node inherits the label of the corresponding bot in the corresponding data mine."
-        },
-        {
-            "style": "Note",
-            "text": "See the data product node definition and the Adding a Data Product Node section for all the details."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/calculations-procedure.json

@@ -21,14 +21,6 @@
         {
             "style": "Note",
             "text": "To fully understand the role of the calculations procedure, please refer to the data mining workflow page."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Calculations Procedure"
-        },
-        {
-            "style": "Text",
-            "text": "To add a calculations procedure, select Add Missing Items on the product definition node menu. Items that may be missing are created along with the basic structure of nodes required to define them."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/cancel-order-event.json

@@ -9,14 +9,6 @@
         {
             "style": "Text",
             "text": "The cancel order event defines the market situations in which a limit order shall be canceled. When the event is triggered, the order is closed, even when the order may have been partially filled. In such a case, the size filled remains as is, and all accounts are computed accordingly, with the partial fill."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Cancel Order Event"
-        },
-        {
-            "style": "Text",
-            "text": "To add the cancel order event node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/cancel-order.json

@@ -1,14 +1,5 @@
 {
     "type": "Cancel Order",
     "definition": "Counts the periods since the last time an order was canceled.",
-    "paragraphs": [
-        {
-            "style": "Title",
-            "text": "Adding a Cancel Order"
-        },
-        {
-            "style": "Text",
-            "text": "To add the cancel order node, select Add Missing Items on the parent node menu."
-        }
-    ]
+    "paragraphs": []
 }

Projects/Superalgos/Schemas/Docs-Nodes/candle.json

@@ -1,14 +1,5 @@
 {
     "type": "Candle",
     "definition": "The candle structure of nodes stores the properties that make up each candle in the episode, including open and close datetime, and the rates for open, min, max, and close.",
-    "paragraphs": [
-        {
-            "style": "Title",
-            "text": "Adding a Candle"
-        },
-        {
-            "style": "Text",
-            "text": "To add the candle node, select Add Missing Items on the parent node menu."
-        }
-    ]
+    "paragraphs": []
 }

Projects/Superalgos/Schemas/Docs-Nodes/chart-points.json

@@ -9,14 +9,6 @@
         {
             "style": "Text",
             "text": "The definition of a point consists of the name of the point and the corresponding values for the x and y coordinates. To create such definitions, point and point formulas are used."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Chart Points"
-        },
-        {
-            "style": "Text",
-            "text": "To add a chart points node, select Add Chart Points on the shapes menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/close-execution.json

@@ -9,14 +9,6 @@
         {
             "style": "Text",
             "text": "The close execution section of the close stage works similarly to the open execution in the open stage. Please refer to the explanations of the open stage for the details."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Close Execution"
-        },
-        {
-            "style": "Text",
-            "text": "To add a close execution node, select Add Close Execution on the open stage node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/close-order.json

@@ -1,14 +1,5 @@
 {
     "type": "Close Order",
     "definition": "Counts the periods since the last time an order was closed.",
-    "paragraphs": [
-        {
-            "style": "Title",
-            "text": "Adding a Close Order"
-        },
-        {
-            "style": "Text",
-            "text": "To add the close order node, select Add Missing Items on the parent node menu."
-        }
-    ]
+    "paragraphs": []
 }

Projects/Superalgos/Schemas/Docs-Nodes/close-position.json

@@ -1,14 +1,5 @@
 {
     "type": "Close Position",
     "definition": "Counts the periods since the last time a position was closed.",
-    "paragraphs": [
-        {
-            "style": "Title",
-            "text": "Adding a Close Position"
-        },
-        {
-            "style": "Text",
-            "text": "To add the close position node, select Add Missing Items on the parent node menu."
-        }
-    ]
+    "paragraphs": []
 }

Projects/Superalgos/Schemas/Docs-Nodes/close-stage-event.json

@@ -13,14 +13,6 @@
         {
             "style": "Text",
             "text": "However, Superalgos allows an extra level of control so that the user may choose to close either stage given specific market situations. Such is the intent of the close stage event."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Close Stage Event"
-        },
-        {
-            "style": "Text",
-            "text": "To add the close stage event node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/close-stage.json

@@ -17,18 +17,6 @@
         {
             "style": "Text",
             "text": "For example, in the open stage, you probably defined the target size as a function of the capital allocated to the trading system. In the close stage, you will likely want to define the target size as a function of the size filled, that is, the amount of the orders placed that was filled during the open stage."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Close Stage"
-        },
-        {
-            "style": "Text",
-            "text": "To add a close stage node, select Add Missing Stages on the strategy node menu. All stages that may be missing are created along with the rest of the basic structure of nodes required to define each of them and their events."
-        },
-        {
-            "style": "Note",
-            "text": "Only one close stage may exist in each strategy."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/close.json

@@ -1,14 +1,5 @@
 {
     "type": "Close",
     "definition": "Close is the rate at the datetime of the end property, as provided by the exchange. That is, the rate at the close of the candle.",
-    "paragraphs": [
-        {
-            "style": "Title",
-            "text": "Adding a Close"
-        },
-        {
-            "style": "Text",
-            "text": "To add the close node, select Add Missing Items on the parent node menu."
-        }
-    ]
+    "paragraphs": []
 }

Projects/Superalgos/Schemas/Docs-Nodes/condition.json

@@ -33,14 +33,6 @@
         {
             "style": "Note",
             "text": "To learn how to write conditions, start with the Syntax Overview."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Condition"
-        },
-        {
-            "style": "Text",
-            "text": "To add a condition, select Add Condition on the corresponding situation node menu. A condition with its JavaScript code node is added."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/create-order-event.json

@@ -17,14 +17,6 @@
         {
             "style": "Text",
             "text": "If you wish orders to be placed as defined immediately after the take position event has been triggered, the use the statement true your only create order event condition."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Create Order Event"
-        },
-        {
-            "style": "Text",
-            "text": "To add the create order event node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/create-order.json

@@ -1,14 +1,5 @@
 {
     "type": "Create Order",
     "definition": "Counts the periods since the last time an order was created.",
-    "paragraphs": [
-        {
-            "style": "Title",
-            "text": "Adding a Create Order"
-        },
-        {
-            "style": "Text",
-            "text": "To add the create order node, select Add Missing Items on the parent node menu."
-        }
-    ]
+    "paragraphs": []
 }

Projects/Superalgos/Schemas/Docs-Nodes/crypto-exchange.json

@@ -3,12 +3,8 @@
     "definition": "A crypto exchange node holds the definitions of assets and markets in a specific exchange.",
     "paragraphs": [
         {
-            "style": "Title",
-            "text": "Adding a Crypto Exchange"
-        },
-        {
-            "style": "Text",
-            "text": "To add a crypto exchange, select Add Crypto Exchange on the crypto exchanges node menu. The crypto exchange node is created along with the rest of the basic structure of nodes required to define assets, markets and user accounts."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/crypto-exchanges.json

@@ -1,18 +1,5 @@
 {
     "type": "Crypto Exchanges",
     "definition": "The crypto exchanges node groups definitions of the different exchanges the user may interact with.",
-    "paragraphs": [
-        {
-            "style": "Title",
-            "text": "Adding a Crypto Exchanges"
-        },
-        {
-            "style": "Text",
-            "text": "To add a crypto exchanges node, select Add Crypto Exchanges on the crypto ecosystem node menu."
-        },
-        {
-            "style": "Note",
-            "text": "Only one crypto exchanges node may exist on the hierarchy."
-        }
-    ]
+    "paragraphs": []
 }

Projects/Superalgos/Schemas/Docs-Nodes/current.json

@@ -17,14 +17,6 @@
         {
             "style": "Text",
             "text": "In other words, the episode, strategy and position nodes within the current section of the hierarchy feature information relative to the instances of the episode, strategy, and position that are currently passing, at any point in time."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Current"
-        },
-        {
-            "style": "Text",
-            "text": "To add the current node, select Add Missing Items on the trading engine node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/cycle.json

@@ -19,12 +19,8 @@
             "text": "The two possible values for the cycle node are First and Second."
         },
         {
-            "style": "Title",
-            "text": "Adding a Cycle"
-        },
-        {
-            "style": "Text",
-            "text": "To add the cycle node, select Add Missing Items on the parent node menu."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/dashboard.json

@@ -13,14 +13,6 @@
         {
             "style": "Text",
             "text": "At the moment, the functionality of a dashboard is trivial: grouping time machines. However, in the future, it will offer various features to enhance the user experience."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Dashboard"
-        },
-        {
-            "style": "Text",
-            "text": "To add a dashboard, select Add Dashboard on the Charting Space node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/data-building-procedure.json

@@ -9,14 +9,6 @@
         {
             "style": "Text",
             "text": "This procedure holds the core logic of the bot, as it features the code that performs the calculations required to produce the new data set. The code is split between a procedure initialization and a procedure loop."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Data Building Procedure"
-        },
-        {
-            "style": "Text",
-            "text": "To add a data buildings procedure, select Add Missing Items on the product definition node menu. Items that may be missing are created along with the basic structure of nodes required to define them."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/data-dependency-folder.json

@@ -11,16 +11,8 @@
             "text": "The use of product data dependency folders is optional, as data dependencies may also exist outside of folders."
         },
         {
-            "style": "Title",
-            "text": "Adding a Data Dependency Folder"
-        },
-        {
-            "style": "Text",
-            "text": "To add the data dependency folder node, select Add Data Dependency Folder on the parent node menu."
-        },
-        {
-            "style": "Text",
-            "text": "The data dependency folder node may be added automatically when using the Add All Data Dependencies option on the data mine data dependencies node menu."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/data-dependency.json

@@ -17,30 +17,6 @@
         {
             "style": "Text",
             "text": "The image above shows data dependencies in one bot referencing dataset definitions of another bot."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Data Dependency"
-        },
-        {
-            "style": "Text",
-            "text": "To add a single data dependency, select Add Data Dependency on the process dependencies, bot data dependencies, or data dependency folder node menus."
-        },
-        {
-            "style": "Text",
-            "text": "{% include tip.html content=\"Remember that a data dependency must establish a reference to the appropriate dataset definition. When adding data dependencies manually, you also need to manually establish the reference.\" %}"
-        },
-        {
-            "style": "Text",
-            "text": "In cases in which multiple data dependencies must be established, you may use the option to create data dependencies in bulk:"
-        },
-        {
-            "style": "Text",
-            "text": " The Add All Data Dependencies* option on the data mine data dependencies node menu adds a bot data dependency for each bot in the data mine, and a data dependency for each dataset definition or each product of each bot. You may use this option after manually adding a data mine data dependencies node and manually establishing the reference with the desired data mine, or after adding all data mine data dependencies, by which the references with data mines are established automatically."
-        },
-        {
-            "style": "Text",
-            "text": "It is unlikely that a bot requires numerous data dependencies, thus, the most common scenario is setting up individual data dependencies and establishing references manually. However, if your bot requires multiple data dependencies, the bulk features may be quite useful, as you may create all data dependencies for any given data mine, and simply delete those that are not required."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/data-formula.json

@@ -1,14 +1,5 @@
 {
     "type": "Data Formula",
     "definition": "A data formula is a device used to assign a value to the panel data, usually in the form of the name of the corresponding record property.",
-    "paragraphs": [
-        {
-            "style": "Title",
-            "text": "Adding a Data Formula"
-        },
-        {
-            "style": "Text",
-            "text": "To add a data formula, select Add Data Formula on the plotter panel menu."
-        }
-    ]
+    "paragraphs": []
 }

Projects/Superalgos/Schemas/Docs-Nodes/data-mine-data-dependencies.json

@@ -11,20 +11,8 @@
             "text": "The node may be used as an organizational device, simply to arrange bot data dependencies. However, the smart use of the node involves automating the deployment of multiple data dependencies and their references."
         },
         {
-            "style": "Title",
-            "text": "Adding a Data Mine Data Dependencies"
-        },
-        {
-            "style": "Text",
-            "text": "To add a data mine data dependencies node, select Add Data Mine Data Dependencies on the parent node menu. This action adds the node but does not establish a reference with any data mine."
-        },
-        {
-            "style": "Text",
-            "text": "The smarter use of the node involves using the Add All Data Mine Dependencies option on the parent node menu. This action creates a data mine data dependencies node for each data mine in the workspace, establishing a reference with the corresponding data mines. This is the first step in the direction of quickly setting up multiple data dependencies when needed."
-        },
-        {
-            "style": "Note",
-            "text": "See the data dependency node definition and the Adding a Data Dependecy Node section for all the details."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/data-mine-products.json

@@ -15,20 +15,8 @@
             "text": "The use of the data mine products node is optional, as data products may also exist outside of data mine products nodes."
         },
         {
-            "style": "Title",
-            "text": "Adding a Data Mine Products"
-        },
-        {
-            "style": "Text",
-            "text": "To add a data mine products node, select Add Data Mine Products on the parent node menu. This action adds the node but does not establish a reference with any data mine."
-        },
-        {
-            "style": "Text",
-            "text": "The smarter use of the node involves using the Add All Data Mine Products option on the parent node menu. This action creates a data mine products node for each data mine in the workspace, establishing a reference with the corresponding data mines. This is the first step in the direction of quickly setting up multiple data products when needed."
-        },
-        {
-            "style": "Note",
-            "text": "See the data product node definition and the Adding a Data Product Node section for all the details."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/data-mine-tasks.json

@@ -11,20 +11,8 @@
             "text": "The data mine tasks node must reference the definition of a data mine. The node may spawn tasks for each bot in the data mine."
         },
         {
-            "style": "Title",
-            "text": "Adding a Data Mine Tasks"
-        },
-        {
-            "style": "Text",
-            "text": "To add a data mine tasks node, select Add Data Mine Tasks on the parent node menu. This action adds the node but does not establish a reference with any data mine."
-        },
-        {
-            "style": "Text",
-            "text": "The smarter use of the node involves using the Add Missing Data Mine Tasks option on the parent node menu. This action creates a data mine tasks node for each data mine in the workspace, establishing a reference with the corresponding data mines. This is the first step in the direction of quickly setting up tasks for each bot in a given data mine."
-        },
-        {
-            "style": "Note",
-            "text": "See the task node definition and the Adding a Task Node section for all the details."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",
@@ -34,6 +22,10 @@
             "style": "Text",
             "text": "Select Configure on the menu to access the configuration."
         },
+        {
+            "style": "Block",
+            "text": "Running"
+        },
         {
             "style": "Title",
             "text": "Running Data Mine Tasks"

Projects/Superalgos/Schemas/Docs-Nodes/data-mine.json

@@ -15,12 +15,8 @@
             "text": "Because the hierarchy provides definitions, it does not intervene in the execution of bots. Instead, the definitions in data mines are instantiated from the network hierarchy by bot instances. Bot instances and process instances are the ones running the code according to the definitions in the corresponding data mine."
         },
         {
-            "style": "Title",
-            "text": "Adding a Data Mine"
-        },
-        {
-            "style": "Text",
-            "text": "To add a data mine, select Add Data Mine on the mines node menu in the Superalgos Project hierarchy."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/data-mines-data.json

@@ -17,18 +17,6 @@
         {
             "style": "Text",
             "text": "Whenever you create data mining tasks manually from within the Network hierarchy (as opposed to using the install market function under the exchange markets node of the Crypto Ecosystem hierarchy"
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Data Mines Data"
-        },
-        {
-            "style": "Text",
-            "text": "To add a session-independent data node, select Add Session-independent Data on the network node menu."
-        },
-        {
-            "style": "Note",
-            "text": "Only one session-independent data node may exist on each data storage node."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/data-product-folder.json

@@ -11,12 +11,8 @@
             "text": "The use of the data product folder node is optional, as data products may also exist outside of data product folders."
         },
         {
-            "style": "Title",
-            "text": "Adding a Data Product Folder"
-        },
-        {
-            "style": "Text",
-            "text": "To add the data product folder node, select Add Data Product Folder on the parent node menu."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/data-product.json

@@ -17,34 +17,6 @@
         {
             "style": "Important",
             "text": "Data products may only be stored on the same network node on which the task—data mining or trading—runs."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Data Product"
-        },
-        {
-            "style": "Text",
-            "text": "To add a single data product, select Add Data Product on the market trading products, market data products, bot products, or data products folder node menus."
-        },
-        {
-            "style": "Note",
-            "text": "Remember to establish a reference with a product definition of the corresponding bot in the corresponding data or trading mine."
-        },
-        {
-            "style": "Text",
-            "text": "In cases in which multiple data products must be added, you may use the option to create data products in bulk."
-        },
-        {
-            "style": "Text",
-            "text": "Select the Add All Data Products option on the data or trading mine products node menu. This adds a bot products node for each bot in the data or trading mine, and a data product for each product definition of each bot."
-        },
-        {
-            "style": "Text",
-            "text": "You may use this option after manually adding a data or trading mine products node and manually establishing the reference with the desired data mine, or after adding all data or trading mine data products, by which the references with data or trading mines are established automatically."
-        },
-        {
-            "style": "Text",
-            "text": "{% include tip.html content=\"If adding data products in bulk results in adding data products that are not required, you may easily delete those.\" %}"
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/data-storage.json

@@ -29,18 +29,6 @@
         {
             "style": "Text",
             "text": "{% include node-deletion-warning.html %}"
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Data Storage"
-        },
-        {
-            "style": "Text",
-            "text": "To add a data storage, select Add Data Storage on the network node menu."
-        },
-        {
-            "style": "Note",
-            "text": "Only one data storage node may exist on each network node."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/dataset-definition.json

@@ -1,6 +1,6 @@
 {
     "type": "Dataset Definition",
-    "definition": "A dataset definition contains a configuration file that defines many aspects of the dataset. There are two types of dataset definitions: Multi-Period-Market and Multi-Period-Daily.",
+    "definition": "A data set is a collection of files stored in the designated location, as per the definitions on the referenced data product in the corresponding data mine.",
     "paragraphs": [
         {
             "style": "Block",
@@ -11,12 +11,8 @@
             "text": "A good part of what makes datasets easy to consume by other bots is the fact that they are standardized in terms of their structure. It is that structure that is specified in the dataset definitions."
         },
         {
-            "style": "Title",
-            "text": "Adding a Dataset Definition"
-        },
-        {
-            "style": "Text",
-            "text": "To add a dataset definition, select Add Dataset Definition on the bot's node menu."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/days.json

@@ -13,14 +13,6 @@
         {
             "style": "Text",
             "text": "In the context of a position, it counts the number of days a position has been open."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Days"
-        },
-        {
-            "style": "Text",
-            "text": "To add the days node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/design-space.json

@@ -11,12 +11,8 @@
             "text": "Think of the design space as your desktop, or the control room of the system."
         },
         {
-            "style": "Title",
-            "text": "Adding a Design Space"
-        },
-        {
-            "style": "Text",
-            "text": "To add the design space node, select Add Design Space on the spaces node of the Superalgos Project hierarchy."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/distance-to-event.json

@@ -9,14 +9,6 @@
         {
             "style": "Text",
             "text": "The information may be used from within strategies, for example, to leave a cool-down period in-between positions, to separate orders in specific intervals, or to achieve any particular logic that may require counting how much time has passed since the last time a specific event was triggered."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Distance To Event"
-        },
-        {
-            "style": "Text",
-            "text": "To add the distance to event node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/dynamic-indicators.json

@@ -1,14 +1,5 @@
 {
     "type": "Dynamic Indicators",
     "definition": "",
-    "paragraphs": [
-        {
-            "style": "Title",
-            "text": "Adding a Dynamic Indicators"
-        },
-        {
-            "style": "Text",
-            "text": "To add the dynamic indicators node, select Add Missing Items on the parent node menu."
-        }
-    ]
+    "paragraphs": []
 }

Projects/Superalgos/Schemas/Docs-Nodes/end-balance.json

@@ -13,14 +13,6 @@
         {
             "style": "Text",
             "text": "In the context of a position, it is the balance at the datetime the position was closed."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a End Balance"
-        },
-        {
-            "style": "Text",
-            "text": "To add the end balance node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/end-rate.json

@@ -17,14 +17,6 @@
         {
             "style": "Text",
             "text": "In the context of an episode, it is the close rate of the last closed candle at the moment the episode ends."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a End Rate"
-        },
-        {
-            "style": "Text",
-            "text": "To add the end rate node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/end.json

@@ -13,14 +13,6 @@
         {
             "style": "Text",
             "text": "In every other context, the datetime is given by the datetime of the moment of evaluation. When evaluating a point in time in which the object remains open, end stores the datetime of that moment, because the object existed until that point in time when the value was last being updated. Once the object is closed, the end value is not modified again."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a End"
-        },
-        {
-            "style": "Text",
-            "text": "To add the end node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/entry-target-rate.json

@@ -9,14 +9,6 @@
         {
             "style": "Text",
             "text": "Refresh this concepts by reading about the initial target definitions at the trading system."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Entry Target Rate"
-        },
-        {
-            "style": "Text",
-            "text": "To add the entry target rate node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/entry-target-size.json

@@ -13,14 +13,6 @@
         {
             "style": "Text",
             "text": "Refresh this concepts by reading about the initial target definitions at the trading system."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Entry Target Size"
-        },
-        {
-            "style": "Text",
-            "text": "To add the entry target size node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/episode-base-asset.json

@@ -9,14 +9,6 @@
         {
             "style": "Note",
             "text": "Learn more about how accounts for the base asset and the quoted asset are kept in the base asset and quoted asset page on the trading engine section of the documentation."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Episode Base Asset"
-        },
-        {
-            "style": "Text",
-            "text": "To add the episode base asset node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/episode-counters.json

@@ -1,14 +1,5 @@
 {
     "type": "Episode Counters",
     "definition": "The episode counters node features counters of instances of objects that come to exist during the duration of the episode.",
-    "paragraphs": [
-        {
-            "style": "Title",
-            "text": "Adding a Episode Counters"
-        },
-        {
-            "style": "Text",
-            "text": "To add the episode counters node, select Add Missing Items on the parent node menu."
-        }
-    ]
+    "paragraphs": []
 }

Projects/Superalgos/Schemas/Docs-Nodes/episode-quoted-asset.json

@@ -9,14 +9,6 @@
         {
             "style": "Note",
             "text": "Learn more about how accounts for the base asset and the quoted asset are kept in the base asset and quoted asset page on the trading engine section of the documentation."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Episode Quoted Asset"
-        },
-        {
-            "style": "Text",
-            "text": "To add the episode quoted asset node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/episode-statistics.json

@@ -1,14 +1,5 @@
 {
     "type": "Episode Statistics",
     "definition": "Episode statistics keeps track of several metrics in the context of the episode.",
-    "paragraphs": [
-        {
-            "style": "Title",
-            "text": "Adding a Episode Statistics"
-        },
-        {
-            "style": "Text",
-            "text": "To add the episode statistics node, select Add Missing Items on the parent node menu."
-        }
-    ]
+    "paragraphs": []
 }

Projects/Superalgos/Schemas/Docs-Nodes/episode.json

@@ -33,14 +33,6 @@
         {
             "style": "List",
             "text": "rates describing each candle in the episode, such as the open, close, min and max rates;"
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Episode"
-        },
-        {
-            "style": "Text",
-            "text": "To add the episode node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/exchange-account-asset.json

@@ -9,18 +9,6 @@
         {
             "style": "Text",
             "text": "The exchange account asset is a reference to an asset defined under the exchange assets node."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Exchange Account Asset"
-        },
-        {
-            "style": "Text",
-            "text": "To add an exchange account asset node, select Add Asset on the user assets node menu."
-        },
-        {
-            "style": "Note",
-            "text": "Remember to establish a reference with an asset defined under the exchange assets node."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/exchange-account-key.json

@@ -3,12 +3,8 @@
     "definition": "The exchange account key holds the definition of the key name and secret provided by the corresponding exchange to access the user account via the exchange API.",
     "paragraphs": [
         {
-            "style": "Title",
-            "text": "Adding a Exchange Account Key"
-        },
-        {
-            "style": "Text",
-            "text": "To add an exchange account key, select Add Key on the user keys node menu."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/exchange-accounts.json

@@ -1,18 +1,5 @@
 {
     "type": "Exchange Accounts",
     "definition": "The exchange accounts node groups the different accounts the user may have with the corresponding exchange.",
-    "paragraphs": [
-        {
-            "style": "Title",
-            "text": "Adding a Exchange Accounts"
-        },
-        {
-            "style": "Text",
-            "text": "To add an exchange accounts node, select Add Exchange Account on the crypto exchange node menu. The exchange account node is created along with the basic structure of nodes used to define keys and user assets with the exchange."
-        },
-        {
-            "style": "Note",
-            "text": "Only one exchange accounts node may exist on each exchange."
-        }
-    ]
+    "paragraphs": []
 }

Projects/Superalgos/Schemas/Docs-Nodes/exchange-assets.json

@@ -3,16 +3,8 @@
     "definition": "The exchange assets node groups the definitions of assets.",
     "paragraphs": [
         {
-            "style": "Title",
-            "text": "Adding a Exchange Assets"
-        },
-        {
-            "style": "Text",
-            "text": "To add an exchange assets node, select Add Exchange Assets on the crypto exchanges node menu. The exchange assets node is created along with a first asset."
-        },
-        {
-            "style": "Note",
-            "text": "Only one exchange assets node may exist on each exchange."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/exchange-data-products.json

@@ -15,20 +15,8 @@
             "text": "When representing an exchange featured in the system's icons library, the standard exchange data tasks icon is replaced by the exchange's logo."
         },
         {
-            "style": "Title",
-            "text": "Adding a Exchange Data Products"
-        },
-        {
-            "style": "Text",
-            "text": "To add a specific exchange data products node, select Add Exchange Data Products on the parent node menu."
-        },
-        {
-            "style": "Note",
-            "text": "Remember to establish a reference to the desired exchange in the Crypto Ecosystem hierarchy."
-        },
-        {
-            "style": "Text",
-            "text": "You may also add exchange data products nodes in bulk for all exchanges that may have been previously defined in the Crypto Ecosystem hierarchy. To do that, select Add Missing Exchanges on the parent node menu. An exchange data products node is created for each defined exchange, each with the corresponding reference."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/exchange-data-tasks.json

@@ -15,20 +15,8 @@
             "text": "When representing an exchange featured in the system's icons library, the standard exchange data tasks icon is replaced by the exchange's logo."
         },
         {
-            "style": "Title",
-            "text": "Adding a Exchange Data Tasks"
-        },
-        {
-            "style": "Text",
-            "text": "To add a specific exchange data tasks node, select Add Exchange Data Tasks on the parent node menu."
-        },
-        {
-            "style": "Note",
-            "text": "Remember to establish a reference to the desired exchange in the Crypto Ecosystem hierarchy."
-        },
-        {
-            "style": "Text",
-            "text": "You may also add exchange data tasks node in bulk for all exchanges that may have been previously defined in the Crypto Ecosystem hierarchy. To do that, select Add Missing Exchanges on the parent node menu. An exchange data tasks node is created for each defined exchange, each with the corresponding reference."
+            "style": "Block",
+            "text": "Running"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/exchange-id.json

@@ -13,14 +13,6 @@
         {
             "style": "Text",
             "text": "In the case of limit orders, it is the rate as specified by the formula under the order rate node. If no such definition exists, then limit orders use the default value as well."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Exchange Id"
-        },
-        {
-            "style": "Text",
-            "text": "To add the exchange id node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/exchange-markets.json

@@ -1,18 +1,5 @@
 {
     "type": "Exchange Markets",
     "definition": "The exchange markets node groups the definitions of markets.",
-    "paragraphs": [
-        {
-            "style": "Title",
-            "text": "Adding a Exchange Markets"
-        },
-        {
-            "style": "Text",
-            "text": "To add an exchange markets node, select Add Exchange Markets on the crypto exchange node menu. The exchange markets node is created along with the basic structure of nodes to define the first market."
-        },
-        {
-            "style": "Note",
-            "text": "Only one exchange assets node may exist on each exchange."
-        }
-    ]
+    "paragraphs": []
 }

Projects/Superalgos/Schemas/Docs-Nodes/exchange-orders.json

@@ -17,14 +17,6 @@
         {
             "style": "Text",
             "text": "Each section of the hierarchy must have the definition of as many orders of each type as the trading system is capable of placing concurrently. For example, if the execution algorithm may place up to three limit buy orders to open a position, then three limit orders must exist under the limit buy orders section of the hierarchy. Each order defined in the trading system must reference the data structure of a matching type of order in the trading engine."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Exchange Orders"
-        },
-        {
-            "style": "Text",
-            "text": "To add the exchange orders node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/exchange-trading-products.json

@@ -15,20 +15,8 @@
             "text": "When representing an exchange featured in the system's icons library, the standard exchange trading products icon is replaced by the exchange's logo."
         },
         {
-            "style": "Title",
-            "text": "Adding a Exchange Trading Products"
-        },
-        {
-            "style": "Text",
-            "text": "To add a specific exchange trading products node, select Add Exchange Trading Products on the parent node menu."
-        },
-        {
-            "style": "Note",
-            "text": "Remember to establish a reference to the desired exchange in the Crypto Ecosystem hierarchy."
-        },
-        {
-            "style": "Text",
-            "text": "You may also add exchange trading products nodes in bulk for all exchanges that may have been previously defined in the Crypto Ecosystem hierarchy. To do that, select Add Missing Exchanges on the trading mines data node menu. An exchange trading products node is created for each defined exchange, each with the corresponding reference."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/exchange-trading-tasks.json

@@ -15,20 +15,8 @@
             "text": "When representing an exchange featured in the system's icons library, the standard exchange trading tasks icon is replaced by the exchange's logo."
         },
         {
-            "style": "Title",
-            "text": "Adding a Exchange Trading Tasks"
-        },
-        {
-            "style": "Text",
-            "text": "To add a specific exchange trading tasks node, select Add Exchange Trading Tasks on the parent node menu."
-        },
-        {
-            "style": "Note",
-            "text": "Remember to establish a reference to the desired exchange in the Crypto Ecosystem hierarchy."
-        },
-        {
-            "style": "Text",
-            "text": "You may also add exchange trading tasks node in bulk for all exchanges that may have been previously defined in the Crypto Ecosystem hierarchy. To do that, select Add Missing Exchanges on the parent node menu. An exchange trading tasks node is created for each defined exchange, each with the corresponding reference."
+            "style": "Block",
+            "text": "Running"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/execution-algorithm.json

@@ -23,12 +23,8 @@
             "text": "An execution algorithm is a set of instructions in the sense that the orders defined in each algorithm are themselves the instructions. That is, an execution algorithm is a set of predefined orders which may be created or canceled given specific market situations."
         },
         {
-            "style": "Title",
-            "text": "Adding a Execution Algorithm"
-        },
-        {
-            "style": "Text",
-            "text": "To add the execution algorithm node, select Add Missing Items on the parent node menu."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/execution-finished-event.json

@@ -17,14 +17,6 @@
         {
             "style": "Text",
             "text": "The image above shows a reference established from the execution started event of a process to the execution finished event of another process."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Execution Finished Event"
-        },
-        {
-            "style": "Text",
-            "text": "To add an execution finished event, select Add Missing Items on the process definition node menu. Items that may be missing are created along with the basic structure of nodes required to define them."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/execution-started-event.json

@@ -21,18 +21,6 @@
         {
             "style": "Text",
             "text": "Not setting up this event on a trading session may result in eventual data inconsistencies, as—in theory—the trading bot may run with some indicators up to date and some slightly delayed."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Execution Started Event"
-        },
-        {
-            "style": "Text",
-            "text": "To add an execution started event, select Add Missing Items on the process definition node menu. Items that may be missing are created along with the basic structure of nodes required to define them."
-        },
-        {
-            "style": "Text",
-            "text": "{% include tip.html content=\"Remember that an execution started event must establish a reference to the appropriate execution finished event.\" %}"
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/exit-target-rate.json

@@ -9,14 +9,6 @@
         {
             "style": "Text",
             "text": "Refresh this concepts by reading about the initial target definitions at the trading system."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Exit Target Rate"
-        },
-        {
-            "style": "Text",
-            "text": "To add the exit target rate node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/exit-target-size.json

@@ -13,14 +13,6 @@
         {
             "style": "Text",
             "text": "Refresh this concepts by reading about the initial target definitions at the trading system."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Exit Target Size"
-        },
-        {
-            "style": "Text",
-            "text": "To add the exit target size node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/exit-type.json

@@ -33,14 +33,6 @@
         {
             "style": "List",
             "text": "Closing Stage: the current stage started closing because the Close Stage is opening."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Exit Type"
-        },
-        {
-            "style": "Text",
-            "text": "To add the exit type node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/fails.json

@@ -9,14 +9,6 @@
         {
             "style": "Note",
             "text": "The workings of the fail counts are analogous to the workings of the hits counts, reversing the sign. That is, when profit loss is negative, it is counted as a fail. Please refer to the definition of hits for the details."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Fails"
-        },
-        {
-            "style": "Text",
-            "text": "To add the fails node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/fee-structure.json

@@ -31,12 +31,8 @@
             "text": "The trade hits the take profit target above the Position Rate level, however, due to fees, the trade has a negative 0.32% ROI."
         },
         {
-            "style": "Title",
-            "text": "Adding a Fee Structure"
-        },
-        {
-            "style": "Text",
-            "text": "To add a parameter that may be missing, select Add Missing Params on the parameters node menu."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/fees-paid.json

@@ -17,14 +17,6 @@
         {
             "style": "Text",
             "text": "Exchanges deduct fees from the asset you are receiving. For instance, if you are selling BTC in the BTC-USDT market, then you are receiving USDT, and the exchange will deduct the fees directly from the amount of USDT you are receiving."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Fees Paid"
-        },
-        {
-            "style": "Text",
-            "text": "To add the fees paid node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/formula.json

@@ -153,14 +153,6 @@
         {
             "style": "Text",
             "text": "orderRate()"
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Formula"
-        },
-        {
-            "style": "Text",
-            "text": "To add a formula, select Add Formula on the corresponding parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/forward-testing-session.json

@@ -15,16 +15,8 @@
             "text": "Running a live session requires the setup of a key reference at the market reference. It also requires a live data feed, meaning that the corresponding sensor bot, along with all indicators used by the referenced trading system, must be up and running. Finally, a live session also requires at least 48 hours of historic market data. Bear in mind that the trading system may require even more historic market data to properly analyze the market."
         },
         {
-            "style": "Title",
-            "text": "Adding a Forward Testing Session"
-        },
-        {
-            "style": "Text",
-            "text": "To add a forward testing session, select Add Forward Testing Session on the trading process instance node menu. When a session is added, it is created with the full set of parameters."
-        },
-        {
-            "style": "Note",
-            "text": "After adding a session node, make sure you establish a reference to the trading system you want it to work with."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",
@@ -70,6 +62,10 @@
             "style": "Important",
             "text": "You need to take this into account at the time of defining your positionSize formula. If the formula is a constant, you may easily run out of balance, as only a fraction of the balance will be available for the strategy to use. It may be a good idea to set up your positionSize as a function of your available balance instead."
         },
+        {
+            "style": "Block",
+            "text": "Running"
+        },
         {
             "style": "Title",
             "text": "Running Forward Testing Session"

Projects/Superalgos/Schemas/Docs-Nodes/heartbeats.json

@@ -11,12 +11,8 @@
             "text": "This parameter affects how you see the progress of the trading session below the trading bot instance node on the design space."
         },
         {
-            "style": "Title",
-            "text": "Adding a Heartbeats"
-        },
-        {
-            "style": "Text",
-            "text": "To add a parameter that may be missing, select Add Missing Params on the parameters node menu."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/hit-fail.json

@@ -13,14 +13,6 @@
         {
             "style": "Note",
             "text": "Please refer to the definition of hits for the details."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Hit Fail"
-        },
-        {
-            "style": "Text",
-            "text": "To add the hit fail node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/hit-ratio.json

@@ -9,14 +9,6 @@
         {
             "style": "Text",
             "text": "Hit ratio results from multiplying the number of hits by 100 and dividing it by the number of positions: hit ratio = hits * 100 / positions."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Hit Ratio"
-        },
-        {
-            "style": "Text",
-            "text": "To add the hit ratio node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/hits.json

@@ -17,14 +17,6 @@
         {
             "style": "Note",
             "text": "The consolidated calculations are explained thoroughly in the profit loss node."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Hits"
-        },
-        {
-            "style": "Text",
-            "text": "To add the hits node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/identifier.json

@@ -9,14 +9,6 @@
         {
             "style": "Text",
             "text": "The property is what would be used to access a specific known record."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Identifier"
-        },
-        {
-            "style": "Text",
-            "text": "To add the identifier node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/image-condition.json

@@ -9,14 +9,6 @@
         {
             "style": "Text",
             "text": "The node is optional. When the node is not present in the definition of the image or when the condition validates true, the image is rendered on screen. When the condition validates false the image is not rendered. As such, the node allows dynamically switching the rendering of the corresponding image on and off ."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Image Condition"
-        },
-        {
-            "style": "Text",
-            "text": "To add the image condition node, select Add Image Condition on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/image-position.json

@@ -15,12 +15,8 @@
             "text": "See the configuration for further details."
         },
         {
-            "style": "Title",
-            "text": "Adding a Image Position"
-        },
-        {
-            "style": "Text",
-            "text": "To add the image position node, select Add Image Position on the parent node menu."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/image.json

@@ -23,12 +23,8 @@
             "text": "See the configuration for further details."
         },
         {
-            "style": "Title",
-            "text": "Adding a Image"
-        },
-        {
-            "style": "Text",
-            "text": "To add the image node, select Add Image on the parent node menu. "
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/index.json

@@ -13,14 +13,6 @@
         {
             "style": "Text",
             "text": "Trading systems may feature more than one strategy. In the context of a strategy, index is the position of the strategy within the trading system."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Index"
-        },
-        {
-            "style": "Text",
-            "text": "To add the index node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/indicator-bot-instance.json

@@ -15,12 +15,8 @@
             "text": "The indicator bot instance holds no definitions as to what the bot does. Instead, its processes instances reference the process definitions in the corresponding data mine. That is how the indicator bot instance obtains the information of what it needs to do once it is run."
         },
         {
-            "style": "Title",
-            "text": "Adding a Indicator Bot Instance"
-        },
-        {
-            "style": "Text",
-            "text": "To add an indicator bot instance, select Add Indicator Bot Instance on the task node menu."
+            "style": "Block",
+            "text": "Running"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/indicator-bot.json

@@ -15,12 +15,8 @@
             "text": "Most of the behavior expected from an indicator bot is defined by the structure of nodes in the hierarchy and the references among the nodes within these definitions. As such, you do not need to code any of the functions that make up the infrastructure functionality. Dependencies, outputs, data structures, execution sequences, and several other problems are handled by the definitions embodied in the structure of nodes that make up an indicator, and are configured in the visual environment of the design space. Coding is limited to the actual calculation and data building procedures."
         },
         {
-            "style": "Title",
-            "text": "Adding a Indicator Bot"
-        },
-        {
-            "style": "Text",
-            "text": "To add an indicator bot, select Add Indicator Bot on the data mine node menu. An indicator bot is created along with the basic structure of nodes required to define it."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/indicator-function.json

@@ -1,14 +1,5 @@
 {
     "type": "Indicator Function",
     "definition": "",
-    "paragraphs": [
-        {
-            "style": "Title",
-            "text": "Adding a Indicator Function"
-        },
-        {
-            "style": "Text",
-            "text": "To add the indicator function node, select Add Missing Items on the parent node menu."
-        }
-    ]
+    "paragraphs": []
 }

Projects/Superalgos/Schemas/Docs-Nodes/indicator-process-instance.json

@@ -15,12 +15,8 @@
             "text": "Once the reference is established, the indicator process instance adopts the name of the process definition it references."
         },
         {
-            "style": "Title",
-            "text": "Adding a Indicator Process Instance"
-        },
-        {
-            "style": "Text",
-            "text": "To add an indicator process instance, select Add Indicator Process Instance on the indicator bot instance node menu."
+            "style": "Block",
+            "text": "Running"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/initial-targets.json

@@ -1,14 +1,5 @@
 {
     "type": "Initial Targets",
     "definition": "The initial targets node holds the most basic definitions about the position to be taken: the target rate and the target size.",
-    "paragraphs": [
-        {
-            "style": "Title",
-            "text": "Adding a Initial Targets"
-        },
-        {
-            "style": "Text",
-            "text": "To add the initial targets node, select Add Missing Items on the parent node menu."
-        }
-    ]
+    "paragraphs": []
 }

Projects/Superalgos/Schemas/Docs-Nodes/javascript-code.json

@@ -13,14 +13,6 @@
         {
             "style": "Important",
             "text": "Until a robust JavaScript editor is implemented on the UI, it is recommended to write code on an external editor and paste it in the UI code bubble to ensure consistency."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Javascript Code"
-        },
-        {
-            "style": "Text",
-            "text": "To add a JavaScript code node, select Add Code on the corresponding parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/key-reference.json

@@ -25,18 +25,6 @@
         {
             "style": "Important",
             "text": "Most exchanges do not allow the same exchange account key to be used with multiple processes querying the exchange API. This means that if you are trading with multiple trading systems or multiple sessions on the same exchange, each session requires different exchange account keys."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Key Reference"
-        },
-        {
-            "style": "Text",
-            "text": "To add a key reference, select Add Key Reference on the task node menu."
-        },
-        {
-            "style": "Note",
-            "text": "Remember to establish a reference with a valid exchange account key after creating the key reference."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/last.json

@@ -25,14 +25,6 @@
         {
             "style": "List",
             "text": "From within a trading system, your strategies may make decisions factoring in what happened with the last position or strategy. For example, you may want to affect the size of the next position depending on the result of the last one."
-        },
-        {
-            "style": "Title",
-            "text": "Adding a Last"
-        },
-        {
-            "style": "Text",
-            "text": "To add the last node, select Add Missing Items on the parent node menu."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Nodes/layer-manager.json

@@ -11,12 +11,8 @@
             "text": "In other words, you use the layers manager node to configure which data products you wish to be made available for visualization purposes on the charts, in particular, on a specific timeline chart to which the layers manager node is attached to."
         },
         {
-            "style": "Title",
-            "text": "Adding a Layer Manager"
-        },
-        {
-            "style": "Text",
-            "text": "To add a layers manager, select Add Layers Manager on the preferred timeline chart node menu."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/layer.json

@@ -11,16 +11,8 @@
             "text": "To set up a layer, you need to establish a reference with the data product of your choice."
         },
         {
-            "style": "Title",
-            "text": "Adding a Layer"
-        },
-        {
-            "style": "Text",
-            "text": "To add a layer, select Add Layer on the layer manager node menu."
-        },
-        {
-            "style": "Note",
-            "text": "After adding a layer node, make sure you establish a reference to the corresponding data product in the data storage node of the network hierarchy."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",
@@ -54,6 +46,10 @@
             "style": "Text",
             "text": " showPanels may be true or false; true shows the plotter panel that may be associated with the data product as per the plotter module definitions; false* makes panels invisible."
         },
+        {
+            "style": "Block",
+            "text": "Charts"
+        },
         {
             "style": "Title",
             "text": "Layer at the Charts"

Projects/Superalgos/Schemas/Docs-Nodes/limit-buy-order.json

@@ -35,12 +35,8 @@
             "text": "{% include tip.html content=\"Please read the definition of market buy order for relevant information about how orders in general work, in particular, the section about Order Size, Filling of Orders, Closing of Orders, and Spawning Multiple Orders. \" %}"
         },
         {
-            "style": "Title",
-            "text": "Adding a Limit Buy Order"
-        },
-        {
-            "style": "Text",
-            "text": "To add the limit buy order node, select Add Missing Items on the parent node menu."
+            "style": "Block",
+            "text": "Configuring"
         },
         {
             "style": "Title",

Projects/Superalgos/Schemas/Docs-Nodes/limit-buy-orders.json

@@ -1,14 +1,5 @@
 {
     "type": "Limit Buy Orders",
     "definition": "Limit buy orders is the section of the data structure that keeps track of this specific type of order.",
-    "paragraphs": [
-        {
-            "style": "Title",
-            "text": "Adding a Limit Buy Orders"
-        },
-        {
-            "style": "Text",
-            "text": "To add the limit buy orders node, select Add Missing Items on the parent node menu."
-        }
-    ]
+    "paragraphs": []
 }