Fix typos

core/group_update_system.py

@@ -58,7 +58,7 @@ def control_center(event):
 
 class GroupUpdateTree(us.UpdateTree):
     """Group trees has their own update method separate from main tree to have
-    more nice profiling statistics. Also, it keeps some specific to grop trees
+    more nice profiling statistics. Also, it keeps some specific to group trees
     statuses."""
     get: Callable[['GrTree'], 'GroupUpdateTree']  # type hinting does not work grate :/
 

core/update_system.py

@@ -423,10 +423,10 @@ def update_animation(cls, event: ev.AnimationEvent):
 
     @classmethod
     def main_update(cls, tree: NodeTree, update_nodes=True, update_interface=True) -> Generator['SvNode', None, None]:
-        """Thi generator is for the triggers. It can update outdated nodes and
+        """This generator is for the triggers. It can update outdated nodes and
         update UI. Should be used only with main trees, the group trees should
-        use different method to separate profiling statistics. Whe it called the
-        tree should have information of what is outdated"""
+        use different method to separate profiling statistics. When it's called
+        the tree should have information of what is outdated"""
 
         # print(f"UPDATE NODES {event.type=}, {event.tree.name=}")
         up_tree = cls.get(tree, refresh_tree=True)
@@ -552,7 +552,7 @@ def __sort_nodes(self,
                      from_nodes: frozenset['SvNode'] = None,
                      to_nodes: frozenset['SvNode'] = None)\
                      -> list[tuple['SvNode', list[NodeSocket]]]:
-        """Sort nodes of the tree in proper execution order. Whe all given
+        """Sort nodes of the tree in proper execution order. When all given
         parameters are None it uses all tree nodes
         :from_nodes: if given it sorts only next nodes from given ones
         :to_nodes: if given it sorts only previous nodes from given

docs/contributing/node_api.rst

@@ -331,7 +331,7 @@ idea. Now it's only used in Dictionary output node. The problem is that this can
 easily lead to losses of user connections what breaks node setups. For example
 in Geometry Nodes project there was a decision that sockets should be
 independent to data layer. So to generate such nodes is not recommended now.
-If there is now way but to have this functionality possible solution could be
+If there is no way but to have this functionality possible solution could be
 to add a button to a node which would recreate sockets explicitly.
 
 .. code-block:: python
@@ -555,7 +555,7 @@ There are helping functions / generators to perform data matching in
 .. _experimental_vectorization:
 
 .. note::
-   There are two experimental approaches to automatize data matching. One can
+   There are two experimental approaches to automate data matching. One can
    be found in ``utils.nodes_mixins.recursive_nodes`` and another in
    ``utils.vectorize`` modules. Both of them can handle not only list of
    objects but and nested to each other lists of objects with arbitrary
@@ -575,7 +575,7 @@ There are helping functions / generators to perform data matching in
 .. note::
    In future vectorization should leve the nodes area and arrive to execution
    system. In this case nodes only have to add information to sockets to give to
-   execution system to now how to match data.
+   execution system to know how to match data.
 
 Data structure
 ^^^^^^^^^^^^^^
@@ -696,7 +696,7 @@ from ``utils.logging`` module or by using ``node.debug``, ``node.info`` and
 other aliases.
 
 If a node rises an error it will appear in console in next format: ``data and
-time [loging level] module name:line number : error name``
+time [logging level] module name:line number : error name``
 
 Traceback is switch off for all logging levels except debug one. If you need it
 make sure that you have appropriate logging level in the settings.
@@ -886,7 +886,7 @@ Improve existing node
 ^^^^^^^^^^^^^^^^^^^^^
 
 First is when you add extra functionality to some node. It's possible by adding
-extra buttons, sockets, modes. Whe you add something like this you should ensure
+extra buttons, sockets, modes. When you add something like this you should ensure
 that default behaviour will be unchanged.
 
 New socket, in most cases, can be placed anywhere among existing ones but it

docs/nodes/analyzer/select_similar.rst

@@ -44,7 +44,7 @@ This node has the following parameters:
     * **Perimeter**. Faces with similar perimeter.
     * **Normal**. Faces with similar normal vector.
     * **CoPlanar**. Faces nearly coplanar to selected.
-- **Compare by**. Comparasion operator to use. Available values are **=**, **>=**, **<=**.
+- **Compare by**. Comparison operator to use. Available values are **=**, **>=**, **<=**.
 - **Threshold**. Similarity threshold. This parameter can be also provided as input.
 
 Outputs

docs/nodes/analyzer/wave_paint.rst

@@ -50,7 +50,7 @@ This node has the following parameters:
 - **Neighbour faces**. Visible only if **Mode** parameter is set to **Faces**. This defines which faces are considered to be neighbour. The available modes are:
 
     - **By Edge**. Faces that share an edge are considered to be neighbour.
-    - **By Vertex**. Faces that share a vertex are considered to be neigbhour.
+    - **By Vertex**. Faces that share a vertex are considered to be neighbour.
 
 Outputs
 -------

docs/nodes/curve/curve_formula.rst

@@ -62,15 +62,15 @@ This node has the following parameters:
 
 * **Formula 1**, **Formula 2**, **Formula 3**. Formulas for 3 components
   defining curve points in the used coordinate system. Default values define
-  simple helix curve in the carthesian coordinates.
+  simple helix curve in the cartesian coordinates.
 * **Output**. This defined the coordinate system being used, and thus it
   defines the exact meaning of formula parameters. The available modes are:
 
-   * **Carthesian**. Three formulas will define correspondingly X, Y and Z coordinates.
+   * **Cartesian**. Three formulas will define correspondingly X, Y and Z coordinates.
    * **Cylindrical**. Three formulas will define correspondingly Rho, Phi and Z coordinates.
    * **Spherical**. Three formulas will define correspondingly Rho, Phi and Theta coordinates.
 
-   The default mode is **Carthesian**.
+   The default mode is **Cartesian**.
 
 * **Vectorize**. This parameter is available in the N panel only. If enabled,
   then to evaluate formulas for a series of input values, the node will use

docs/nodes/curve/curve_frame.rst

@@ -5,7 +5,7 @@ Functionality
 -------------
 
 This node calculates a reference frame of a curve (also known as Frenet_ frame)
-for the given value of curve's T parameter. Basically, the node allowes one to
+for the given value of curve's T parameter. Basically, the node allows one to
 place some object at the curve, by aligning the object with curve's "natural"
 orientation.
 

docs/nodes/curve/fillet_polyline.rst

@@ -11,7 +11,7 @@ closed or not.
 The curve is generated by plotting a polyline through the points, and then
 rounding all corners by replacing them with circular arc.
 
-Instead of circluar arcs, the node can generate segments of quadratic Bezier
+Instead of circular arcs, the node can generate segments of quadratic Bezier
 curves. This option can be useful, for example, if one of nodes applied later
 can not handle rational NURBS curves.
 

docs/nodes/exchange/FCStd_read_mod.rst

@@ -7,7 +7,7 @@ Functionality
 This node is an experimental modification of the original FCStd Read node.
 This node reads one or more FCStd files, and 
 
-- intputs: Labels can be used to narrow down which objects you wish retrieve from the files.
+- inputs: Labels can be used to narrow down which objects you wish retrieve from the files.
 - outputs: the `obj.Shape` as a Solid socket, it also 
 - outputs: `obj.FullName, obj.Name, obj.Label` in the Names socket.
 

docs/nodes/exchange/bezier_in.rst

@@ -28,7 +28,7 @@ Parameters
 This node has the following parameters:
 
 * **Sort**. If checked, the node will sort selected objects by name. Checked by default.
-* **Apply matricess**. If checked, the node will apply all transforms to
+* **Apply matrices**. If checked, the node will apply all transforms to
   Blender's objects before bringing the coordinates into Sverchok. Checked by
   default.
 * **Concatenate segments**. If checked, join Bezier segments of the curve into

docs/nodes/exchange/export_rw3dm_json.rst

@@ -13,7 +13,7 @@ Functionality
 
 This node allows to export a set of NURBS_ Curve or Surface objects to a
 JSON format, supported by rw3dm_ utility; that utility can be used to convert
-such JSON formath to Rhinoceros ® 3D format.
+such JSON format to Rhinoceros ® 3D format.
 
 .. _rw3dm: https://github.com/orbingol/rw3dm
 .. _NURBS: https://en.wikipedia.org/wiki/Non-uniform_rational_B-spline

docs/nodes/exchange/nurbs_in.rst

@@ -44,7 +44,7 @@ This node has the following parameters:
   The default option is **Geomdl**, when it is available; otherwise, built-in implementation is used.
 
 * **Sort**. If checked, the node will sort selected objects by name. Checked by default.
-* **Apply matricess**. If checked, the node will apply all transforms to
+* **Apply matrices**. If checked, the node will apply all transforms to
   Blender's objects before bringing the coordinates into Sverchok. Checked by
   default.
 

docs/nodes/field/compose_vector_field.rst

@@ -22,7 +22,7 @@ This node has the following parameter:
 
 * **Coordinates**. This defines the coordinate system being used. The available modes are:
 
-  * **Carthesian**. Compose the vector field from X, Y and Z fields.
+  * **Cartesian**. Compose the vector field from X, Y and Z fields.
   * **Cylindrical**. Compose the vector field from Rho, Phi and Z fields.
   * **Spherical**. Compose the vector field from Rho, Phi and Theta fields.
 

docs/nodes/field/coordinate_scalar_field.rst

@@ -8,7 +8,7 @@ This node generates a Scalar Field, the value of which at each point equals to
 one of coordinates of that point. For example, this node can generate a scalar
 field generated by function `S(x,y,z) = x`.
 
-Carthesian, cylindrical and spherical coordinates are supported.
+Cartesian, cylindrical and spherical coordinates are supported.
 
 Inputs
 ------
@@ -22,9 +22,9 @@ This node has the following parameter:
 
 * **Coordinate**. The coordinate to use. The available values are:
 
-  * **X**. Carthesian X coordinate. This option is the default one.
-  * **Y**. Carthesian Y coordinate.
-  * **Z**. Carthesian Z coordinate, or cylindrical Z coordinate - they are identical.
+  * **X**. Cartesian X coordinate. This option is the default one.
+  * **Y**. Cartesian Y coordinate.
+  * **Z**. Cartesian Z coordinate, or cylindrical Z coordinate - they are identical.
   * **Rho - Cylindrical**. Cylindrical Rho coordinate.
   * **Phi**. Cylindrical or spherical Phi coordinate - they are identical.
   * **Rho - Spherical**. Spherical Rho coordinate.

docs/nodes/field/decompose_vector_field.rst

@@ -20,11 +20,11 @@ This node has the following parameter:
 
 * **Coordinates**. This defines the coordinate system to be used. The available options are:
 
-  * **Carthesian**. The vector field is decomposed into X, Y and Z fields.
+  * **Cartesian**. The vector field is decomposed into X, Y and Z fields.
   * **Cylindrical**. The vector field is decomposed into Rho, Phi and Z fields.
   * **Spherical**. The vector field is decomposed into Rho, Phi and Theta fields.
 
-  The default mode is **Carthesian**.
+  The default mode is **Cartesian**.
 
 Outputs
 -------

docs/nodes/field/scalar_field_formula.rst

@@ -56,7 +56,7 @@ Each variable used in the formula, except for `V` and the coordinate variables,
 
 The following variables are considered to be point coordinates:
 
-* For Carthesian mode: `x`, `y` and `z`;
+* For Cartesian mode: `x`, `y` and `z`;
 * For Cylindrical mode: `rho`, `phi` and `z`;
 * For Spherical mode: `rho`, `phi` and `theta`.
 
@@ -67,7 +67,7 @@ This node has the following parameters:
 
 * **Input**. This defines the coordinate system being used. The available
   values are **Carhtesian**, **Cylindrical** and **Spherical**. The default
-  value is **Carthesian**.
+  value is **Cartesian**.
 * **Formula**. The formula which defines the scalar field. The default formula
   is `x*x + y*y + z*z`.
 * **Vectorize**. This parameter is available in the N panel only. If enabled,

docs/nodes/field/vector_field_formula.rst

@@ -58,7 +58,7 @@ also becomes additional input.
 
 The following variables are considered to be point coordinates:
 
-* For Carthesian input mode: `x`, `y` and `z`;
+* For Cartesian input mode: `x`, `y` and `z`;
 * For Cylindrical input mode: `rho`, `phi` and `z`;
 * For Spherical input mode: `rho`, `phi` and `theta`.
 
@@ -74,15 +74,15 @@ This node has the following parameters:
 
 * **Input**. This defines the coordinate system being used for the input
   points. The available values are **Carhtesian**, **Cylindrical** and
-  **Spherical**. The default value is **Carthesian**.
+  **Spherical**. The default value is **Cartesian**.
 * **Formula1**, **Formula2**, **Formula3**. Three formulas defining the
   respective coordinate / components of the resulting vectors: X, Y, Z, or Rho,
   Phi, Z, or Rho, Phi, Theta, depending on the **Output** parameter. The
   default formulas are `-y`, `x` and `z`, which defines the field which rotates
   the whole space 90 degrees around the Z axis.
 * **Output**. This defines the coordinate system in which the resulting vectors
   are expressed. The available values are **Carhtesian**, **Cylindrical** and
-  **Spherical**. The default value is **Carthesian**.
+  **Spherical**. The default value is **Cartesian**.
 * **Vectorize**. This parameter is available in the N panel only. If enabled,
   then to evaluate formulas for a series of input values, the node will use
   NumPy functions to perform several computations at a time; otherwise, the

docs/nodes/field/vector_field_graph.rst

@@ -8,7 +8,7 @@ This node visualizes a Vector Field object by generating arrows (which
 represent vectors) from points of original space to the results of vector field
 application to those original points.
 
-The original points are generated as carthesian grid in 3D space.
+The original points are generated as cartesian grid in 3D space.
 
 This node is mainly intended for visualization.
 
@@ -21,7 +21,7 @@ This node has the following inputs:
 * **Bounds**. The list of points which define the area of space, in which the
   field is to be visualized. Only the bounding box of these points is used.
 * **Scale**. The scale of arrows to be generated. The default value is 1.0.
-* **SamplesX**, **SamplesY**, **SamplesZ**. The number of samples of carthesian
+* **SamplesX**, **SamplesY**, **SamplesZ**. The number of samples of cartesian
   grid, from which the arrows are to be generated. The default value is 10.
 
 Parameters
@@ -30,7 +30,7 @@ Parameters
 This node has the following parameters:
 
 * **Auto scale**. Select the scale of arrows automatically, so that the largest
-  arrows are not bigger than the distance between carthesian grid points.
+  arrows are not bigger than the distance between cartesian grid points.
   Checked by default.
 * **Join**. If checked, then all arrows will be merged into one mesh object.
   Otherwise, separate object will be generated for each arrow. Checked by

docs/nodes/list_struct/start_end.rst

@@ -14,7 +14,7 @@ Inputs
 Properties
 ----------
 
-**level** - leve to take first and last items
+**level** - level to take first and last items
 
 Outputs
 -------

docs/nodes/logic/loop_out.rst

@@ -21,14 +21,14 @@ Inputs
 
 **Skip**: If a True value is inputted the loop the result wont be added to the output, like a internal mask.  (Only if Loop In is in For Each Mode).
 
-Data0, Data1... if working on Range Mode inputs will be created coping the Loop in Outputs. If working in For Each mode they will be created when linking the Loop Out inputs
+Data0, Data1... if working on Range Mode inputs will be created copying the Loop in Outputs. If working in For Each mode they will be created when linking the Loop Out inputs
 
 
 Outputs
 -------
 
 
-Data0, Data1... In Range mode: inputs will be created coping the Loop in Outputs. In For Each mode they will be copy the Loop Out inputs.
+Data0, Data1... In Range mode: inputs will be created copying the Loop in Outputs. In For Each mode they will be copy the Loop Out inputs.
 
 
 Examples

docs/nodes/modifier_make/clip_verts.rst

@@ -5,7 +5,7 @@ Functionality
 -------------
 
 This node cuts off (clips, truncates) all vertices of original mesh, by cutting
-each edge in half, and then connecting centers of all edges incidential to each
+each edge in half, and then connecting centers of all edges incidental to each
 vertex, to produce new faces. Please refer to usage examples for better
 understanding.
 

docs/nodes/modifier_make/diamond_mesh.rst

@@ -5,7 +5,7 @@ Functionality
 -------------
 
 This node generates a new (rhomboidal / diamond-like) mesh, by replacing each
-edge of original mesh by a rhombus (connecting centers of two incidential
+edge of original mesh by a rhombus (connecting centers of two incidental
 faces). This can give interesting topology, especially in combination with
 "dual mesh" and/or "triangulate" and/or "join triangles" and/or "limited
 dissolve" nodes.

docs/nodes/solid/solid_to_mesh_mk2.rst

@@ -31,7 +31,7 @@ Methods
 
 **Trivial**: ...
 
-**Lenient**: This mode is based on Yorik van Havre's Blender FCStd importer code, but modified for speed. This mode produces tris, quads and ngons. It may not have coherent polygon normals. This handles curves and polygons with holes. This mode attemps to remove any duplicate/reverse faces. 
+**Lenient**: This mode is based on Yorik van Havre's Blender FCStd importer code, but modified for speed. This mode produces tris, quads and ngons. It may not have coherent polygon normals. This handles curves and polygons with holes. This mode attempts to remove any duplicate/reverse faces. 
 
 If you really want to understand these algorithms, you should read the source code - it is the best reference.
 

docs/nodes/spatial/field_random_probe.rst

@@ -97,7 +97,7 @@ This node has the following outputs:
 Examples of usage
 -----------------
 
-Generate cubes near the cyllinder:
+Generate cubes near the cylinder:
 
 .. image:: https://user-images.githubusercontent.com/284644/81504481-f2be5900-9302-11ea-8948-fb189c3fc3c5.png
 

docs/nodes/surface/adaptive_tessellate.rst

@@ -7,7 +7,7 @@ Functionality
 This node generates an adaptive tessellation for the given surface, i.e. the
 mesh which represents the surface, and has smaller amount of subdivisions in
 places where the mesh is nearly flat and more subdivisions where the surface
-behaivour is more interesting.
+behaviour is more interesting.
 
 In most cases, one converts a Surface object into a mesh by use of "Evaluate
 Surface" node. That node generates a subdivision by cartesian (rectangular)

docs/nodes/surface/evaluate_surface.rst

@@ -6,7 +6,7 @@ Functionality
 
 This node calculates points on the Surface corresponding to provided values of
 U and V surface parameters. The values of U and V can be either provided
-explicitly, or generated by the node to generate carthesian (rectangular) grid.
+explicitly, or generated by the node to generate cartesian (rectangular) grid.
 
 Inputs
 ------
@@ -23,7 +23,7 @@ This node has the following inputs:
   **Evaluation mode** parameter is set to **Explicit**, and **Input mode** is
   set to **Vertices**.
 * **SamplesU**, **SamplesV**. Number of samples along U and V direction, used
-  to generate carthesian grid. These inputs are available only when the
+  to generate cartesian grid. These inputs are available only when the
   **Evaluate** parameter is set to **Grid**. The default value is 25.
 
 Parameters
@@ -37,7 +37,7 @@ This node has the following parameters:
   * **Explicit**. U and V parameters are to be provided in inputs of this node.
     Depending on **Input mode** parameter, either **U** and **V** inputs, or
     **Vertices** input will be used.
-  * **Grid**. The node will generate evenly-spaced carthesian grid with number
+  * **Grid**. The node will generate evenly-spaced cartesian grid with number
     of samples along U and V direction defined by **SamplesU** and **SamplesV**
     inputs, correspondingly.
 
@@ -90,9 +90,9 @@ Outputs
 This node has the following outputs:
 
 * **Vertices**. The calculated points on the surface.
-* **Edges**. The edges of carthesian grid on the surface. This output is only
+* **Edges**. The edges of cartesian grid on the surface. This output is only
   available when the **Evaluate** parameter is set to **Grid**.
-* **Faces**. The faces of carthesian grid on the surface. This output is only
+* **Faces**. The faces of cartesian grid on the surface. This output is only
   available when the **Evaluate** parameter is set to **Grid**.
 
 Examples of usage