Merge pull request #2466 from krimsonkla/develop

Contribution: "Last of the typos"
2021-11-04 04:02:36 -04:00
commit 347cace378
@@ -9,7 +9,7 @@
    "paragraphs": [
        {
            "style": "Text",
-            "text": "Each type of node, might have a definition with the initial values for it's configuration. The Initial Values are set at the node iwhen the Node is first created. ",
+            "text": "Each type of node, might have a definition with the initial values for it's configuration. The Initial Values are set at the node when the Node is first created. ",
            "updated": 1609244634949
        }
    ]
@@ -9,7 +9,7 @@
    "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 Code.",
+            "text": "Some types of nodes, might have code that defines their behaviour. The code can usually be accessed 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
        }
    ]
@@ -9,7 +9,7 @@
    "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.",
+            "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 has a set of properties that allow the system to execute some action when the menu item is clicked by users.",
            "updated": 1609240463871
        }
    ]
@@ -16,7 +16,7 @@
    "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*.",
+            "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 incompatible types. There is also the possibility to replace the list of types for the keyword *Any Node*.",
            "updated": 1609243750949
        }
    ]
@@ -3,7 +3,7 @@
    "pageNumber": "9",
    "type": "Node Referencing Rules",
    "definition": {
-        "text": "Each Node Type can have a set of rules that defines with which Node Type it can stablish a reference.",
+        "text": "Each Node Type can have a set of rules that defines with which Node Type it can Establish a reference.",
        "updated": 1609244259240,
        "translations": [
            {
@@ -3,7 +3,7 @@
    "pageNumber": "12",
    "type": "Reference Parent",
    "definition": {
-        "text": "The Reference Parent of a certain Node A, is the node with which A stablishes a Reference.",
+        "text": "The Reference Parent of a certain Node A, is the node with which A establishes a Reference.",
        "updated": 1609240205404
    },
    "paragraphs": [