apostrophe problem fixed

This commit is contained in:
Luis Fernando Molina committed 2020-12-30 12:27:20 +01:00
1 parent 15cd349c05
commit 4309c19bb7
13 files changed
+55 -55

No files matched your search

@@ -37,7 +37,7 @@
},
{
"style": "List",
"text": "Vaina 1 Hello What's up? Node's Type",
"text": "Vaina 1 Hello What's up? Node Type",
"updated": 1609232016451,
"translations": [
{
@@ -1,9 +1,9 @@
{
"topic": "Nodes",
"pageNumber": "2",
"type": "Node's Type",
"type": "Node Type",
"definition": {
"text": "Each Node is of a certain type. It's type defines what the Node can be used for, the Node's Menu, to which other nodes it can attach to, and may other properties that are dependent on the Node's Type At the Design Space, the type of the node is displayed below the Node's Icon. ",
"text": "Each Node is of a certain type. It's type defines what the Node can be used for, the Node Menu, to which other nodes it can attach to, and may other properties that are dependent on the Node Type At the Design Space, the type of the node is displayed below the Node Icon. ",
"updated": 1609236288974
},
"paragraphs": [
@@ -1,9 +1,9 @@
{
"topic": "Nodes",
"pageNumber": "3",
"type": "Node's Name",
"type": "Node Name",
"definition": {
"text": "Each instance of a Node might have a user-assigned name, or a default name assigned to it by the system at the moment the Node was created. At the Design Space the name of a Node appears above the Node's Icon. ",
"text": "Each instance of a Node might have a user-assigned name, or a default name assigned to it by the system at the moment the Node was created. At the Design Space the name of a Node appears above the Node Icon. ",
"updated": 1609236312410
},
"paragraphs": [
@@ -1,9 +1,9 @@
{
"topic": "Nodes",
"pageNumber": "4",
"type": "Node's Config",
"type": "Node Config",
"definition": {
"text": "Nodes might have a config -only when needed- that it is used to store information related to that node. When they do, they usually allow users to access it via one of the Node's Menu items. A Node's Config is later used by Tasks or Bots during their processing.",
"text": "Nodes might have a config -only when needed- that it is used to store information related to that node. When they do, they usually allow users to access it via one of the Node Menu items. A Node Config is later used by Tasks or Bots during their processing.",
"updated": 1609236556444
},
"paragraphs": [
@@ -1,15 +1,15 @@
{
"topic": "Nodes",
"pageNumber": "5",
"type": "Node's Code",
"type": "Node Code",
"definition": {
"text": "Nodes might have code inside of them. When they do, they usually allow users to access and modify it via one of the Node's Menu items. The code stored at a node is later used at Tasks or Bots during their processing.",
"text": "Nodes might have code inside of them. When they do, they usually allow users to access and modify it via one of the Node Menu items. The code stored at a node is later used at Tasks or Bots during their processing.",
"updated": 1609236689695
},
"paragraphs": [
{
"style": "Text",
"text": "Some types of nodes, might have code that defines their behaviour. The code can usually be accesed by users via the Edit menu item. When first created, the code of a Node is initialized with the initial value present at the Node's Definition Document. Some types of node represents Formulas and they hold code that defines those formulas at the Node's Code.",
"text": "Some types of nodes, might have code that defines their behaviour. The code can usually be accesed by users via the Edit menu item. When first created, the code of a Node is initialized with the initial value present at the Node's Definition Document. Some types of node represents Formulas and they hold code that defines those formulas at the Node Code.",
"updated": 1609246211297
}
]
@@ -1,16 +0,0 @@
{
"topic": "Nodes",
"pageNumber": "6",
"type": "Node's Menu",
"definition": {
"text": "Nodes usually have a menu that allows users to interact with the node. Each Node's Type can have a different set of menu items. ",
"updated": 1609236892270
},
"paragraphs": [
{
"style": "Text",
"text": "Each Node's Type, might have a menu which allow users to interact with the Node. There is no fixed set of menu items. Instead each menu items is defined at each Node's definition. Each menu item haave a set of properties that allow the system to execute some action when the menu item is clicked by users.",
"updated": 1609240463871
}
]
}
@@ -0,0 +1,16 @@
{
"topic": "Nodes",
"pageNumber": "6",
"type": "Node Menu",
"definition": {
"text": "Nodes usually have a menu that allows users to interact with the node. Each Node Type can have a different set of menu items. ",
"updated": 1609236892270
},
"paragraphs": [
{
"style": "Text",
"text": "Each Node Type, might have a menu which allow users to interact with the Node. There is no fixed set of menu items. Instead each menu items is defined at each Node's definition. Each menu item haave a set of properties that allow the system to execute some action when the menu item is clicked by users.",
"updated": 1609240463871
}
]
}
@@ -1,9 +1,9 @@
{
"topic": "Nodes",
"pageNumber": "7",
"type": "Node's Children",
"type": "Node Children",
"definition": {
"text": "Nodes might have children. When they do, they usually offer the User a way to create it's children via the Node's Menu. A Node's Children might end up attached to the Parent Node, but that is not always the case.",
"text": "Nodes might have children. When they do, they usually offer the User a way to create it's children via the Node Menu. A Node Children might end up attached to the Parent Node, but that is not always the case.",
"updated": 1609237042862
},
"paragraphs": [
@@ -14,7 +14,7 @@
},
{
"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 (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."
"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 Type defines which properties will hold those children references."
}
]
}
@@ -1,16 +0,0 @@
{
"topic": "Nodes",
"pageNumber": "8",
"type": "Node's Attaching Rules",
"definition": {
"text": "Each Node's Type can have a set of rules that defines to which Node's Type it can attach itself to.",
"updated": 1609237513121
},
"paragraphs": [
{
"style": "Text",
"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
}
]
}
@@ -0,0 +1,16 @@
{
"topic": "Nodes",
"pageNumber": "8",
"type": "Node Attaching Rules",
"definition": {
"text": "Each Node Type can have a set of rules that defines to which Node Type it can attach itself to.",
"updated": 1609237513121
},
"paragraphs": [
{
"style": "Text",
"text": "Each Node 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 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
}
]
}
@@ -1,9 +1,9 @@
{
"topic": "Nodes",
"pageNumber": "9",
"type": "Node's Referencing Rules",
"type": "Node Referencing Rules",
"definition": {
"text": "Each Node's Type can have a set of rules that defines with which Node's Type it can stablish a reference.",
"text": "Each Node Type can have a set of rules that defines with which Node Type it can stablish a reference.",
"updated": 1609244259240
},
"paragraphs": [
@@ -1,7 +1,7 @@
{
"topic": "Nodes",
"pageNumber": "10",
"type": "Node's Icon",
"type": "Node Icon",
"definition": {
"text": "Each Node must have a icon, that is the one that represents the Node at the Desing Space.",
"updated": 1609237637368
@@ -2371,7 +2371,7 @@ function newSuperalgosDocSpace() {
autoGeneratedParagraphIndex++
paragraph = {
style: "Text",
text: "The " + appSchemaDocument.type + " Node has the following Node's Menu items:"
text: "The " + appSchemaDocument.type + " Node has the following Node Menu items:"
}
renderParagraph(paragraph, key)
autoGeneratedParagraphIndex++
@@ -2424,7 +2424,7 @@ function newSuperalgosDocSpace() {
autoGeneratedParagraphIndex++
paragraph = {
style: "Text",
text: "The " + appSchemaDocument.type + " Node has the following childrenNodesProperties which hold the Node's Children at runtime:"
text: "The " + appSchemaDocument.type + " Node has the following childrenNodesProperties which hold the Node Children at runtime:"
}
renderParagraph(paragraph, key)
autoGeneratedParagraphIndex++
@@ -2472,7 +2472,7 @@ function newSuperalgosDocSpace() {
autoGeneratedParagraphIndex++
paragraph = {
style: "Text",
text: "The following are Node's Attaching Rules that govern the attacment of " + appSchemaDocument.type + " with other nodes:"
text: "The following are Node Attaching Rules that govern the attacment of " + appSchemaDocument.type + " with other nodes:"
}
renderParagraph(paragraph, key)
autoGeneratedParagraphIndex++
@@ -2527,7 +2527,7 @@ function newSuperalgosDocSpace() {
autoGeneratedParagraphIndex++
paragraph = {
style: "Text",
text: "The following are Node's Referencing Rules that govern to which nodes " + appSchemaDocument.type + " can stablish a reference:"
text: "The following are Node Referencing Rules that govern to which nodes " + appSchemaDocument.type + " can stablish a reference:"
}
renderParagraph(paragraph, key)
autoGeneratedParagraphIndex++
@@ -2581,7 +2581,7 @@ function newSuperalgosDocSpace() {
autoGeneratedParagraphIndex++
paragraph = {
style: "Text",
text: appSchemaDocument.type + " has a Node's Config."
text: appSchemaDocument.type + " has a Node Config."
}
renderParagraph(paragraph, key)
autoGeneratedParagraphIndex++
@@ -2693,7 +2693,7 @@ function newSuperalgosDocSpace() {
autoGeneratedParagraphIndex++
paragraph = {
style: "Text",
text: "In this section we will explore " + appSchemaDocument.type + " Node's Code."
text: "In this section we will explore " + appSchemaDocument.type + " Node Code."
}
renderParagraph(paragraph, key)
autoGeneratedParagraphIndex++
@@ -2789,7 +2789,7 @@ function newSuperalgosDocSpace() {
autoGeneratedParagraphIndex++
paragraph = {
style: "Text",
text: "In this section we will explore " + appSchemaDocument.type + " Node's Code."
text: "In this section we will explore " + appSchemaDocument.type + " Node Code."
}
renderParagraph(paragraph, key)
autoGeneratedParagraphIndex++