Removing text from code

Projects/Superalgos/Schemas/Docs-Concepts/vaina.json

@@ -19,24 +19,24 @@
     },
     "paragraphs": [
         {
-            "style": "Text",
+            "style": "Important",
             "text": "Left click and Edit to enter edit mode and change this text. ENTER to write new paragraphs. ESC to exit edit mode. Task",
             "translations": [
                 {
                     "language": "RU",
                     "text": "Esto esta escrito en ruso.",
-                    "style": "Text"
+                    "style": "Important"
                 },
                 {
                     "language": "ES",
                     "text": "Esto esta en espaniol.",
-                    "style": "Text"
+                    "style": "Important"
                 }
             ],
             "updated": 1609142715653
         },
         {
-            "style": "Text",
+            "style": "List",
             "text": "Vaina 1 Hello What's up? Node's Type",
             "updated": 1609232016451,
             "translations": [
@@ -44,7 +44,7 @@
                     "language": "ES",
                     "text": "Vaina 1 Hola. Que hay?",
                     "updated": 1609084602600,
-                    "style": "Text"
+                    "style": "List"
                 }
             ]
         },

Projects/Superalgos/Schemas/Docs-Topics/nodes-007-node's-children.json

@@ -7,9 +7,14 @@
         "updated": 1609237042862
     },
     "paragraphs": [
+        {
+            "style": "Title",
+            "text": "Children Nodes Properties",
+            "updated": 1609242892197
+        },
         {
             "style": "Text",
-            "text": "Left click and Edit to enter edit mode and change this text. ENTER to write new paragraphs. ESC to exit edit mode."
+            "text": "Each type of node might have children. If they do, a reference to the children will be present at runtime at one or more properties of the node object. There is no generic childrenNodes property (like in HTML) with an array of children nodes. Instead what we can find is that each Node's Type defines which properties will hold those children references."
         }
     ]
 }

Projects/Superalgos/Schemas/Docs-Topics/nodes-008-node's-attaching-rules.json

@@ -9,7 +9,8 @@
     "paragraphs": [
         {
             "style": "Text",
-            "text": "Left click and Edit to enter edit mode and change this text. ENTER to write new paragraphs. ESC to exit edit mode."
+            "text": "Each Node's Type, might have a set of rules that defines to which nodes it can be attached to. These rules are literally two lists of Node's Type s, one for compatible types and the second one for uncompatible types. There is also the possiblity to replace the list of types for the keyword *Any Node*.",
+            "updated": 1609243750949
         }
     ]
 }

Projects/Superalgos/UI/Spaces/Docs-Space/DocsSpace.js

@@ -2402,7 +2402,7 @@ function newSuperalgosDocSpace() {
                     autoGeneratedParagraphIndex++
                     paragraph = {
                         style: "Text",
-                        text: "Each type of node might have children. If they do, a reference to the children will be present at runtime at one or more properties of the node object. There is no generic childrenNodes property with an array of children nodes. Instead what we can find is that each schema document defines which properties will hold those children references. The property names that will be used for that are the ones listed here. The " + appSchemaDocument.type + " node has the following children nodes properties:"
+                        text: "The " + appSchemaDocument.type + " Node has the following childrenNodesProperties which hold the Node's Children at runtime:"
                     }
                     renderParagraph(paragraph, key)
                     autoGeneratedParagraphIndex++
@@ -2450,7 +2450,7 @@ function newSuperalgosDocSpace() {
                     autoGeneratedParagraphIndex++
                     paragraph = {
                         style: "Text",
-                        text: "Each type of node, might have a set of rules that defines to which nodes it can be attached to. Usually the nodes it can attach to have listed at their own definitions " + appSchemaDocument.type + " as one of its potential children. That does not mean that " + appSchemaDocument.type + " can be created at those parents; only if there is a menu item for adding it, then it will be possible, otherwise it might be created at some other node and later attached to one of the nodes defined in these rules. At runtime, the node that a node is attached to, we call it Parent Node. The following are the rules that govern the attacment of  " + appSchemaDocument.type + " with other nodes:"
+                        text: "The following are Node's Attaching Rules that govern the attacment of  " + appSchemaDocument.type + " with other nodes:"
                     }
                     renderParagraph(paragraph, key)
                     autoGeneratedParagraphIndex++
@@ -2505,7 +2505,7 @@ function newSuperalgosDocSpace() {
                     autoGeneratedParagraphIndex++
                     paragraph = {
                         style: "Text",
-                        text: "Each type of node, might have a set of rules that defines to which node it can stablish a reference to. At runtime once a reference is stablished, we call the referenced node the Reference Parent. The following are the rules that govern the referencing of  " + appSchemaDocument.type + " with other nodes:"
+                        text: "The following are Node's Referencing Rules that govern to which nodes " + appSchemaDocument.type + " can stablish a reference:"
                     }
                     renderParagraph(paragraph, key)
                     autoGeneratedParagraphIndex++