grammar fix

docs/user_guide/nodes/mesh/bmesh_from_mesh_data.rst

@@ -3,7 +3,7 @@ Bmesh From Mesh Data
 
 Description
 -----------
-This node convert mesh data block into a Bmesh block.
+This node converts a mesh data block into a Bmesh block.
 
 .. image:: images/bmesh_from_mesh_data_node.png
    :width: 160pt

docs/user_guide/nodes/mesh/bmesh_from_object.rst

@@ -3,9 +3,9 @@ Bmesh From Object
 
 Description
 -----------
-This node return a bmesh data type for the input object.
+This node returns a bmesh data type for the input object.
 
-A bmesh data type is created using blender's bmesh python module which support operations that can't be performed normally in bpy module and thus can't be applied on a normal mesh data type, some of this operations are implimented in AN like **Limited Dissolve** and **Remove Doubles**.
+A bmesh data type is created using blender's bmesh python module which support operations that can't be performed normally in bpy module and thus can't be applied on a normal mesh data type, some of these operations are implimented in AN like **Limited Dissolve** and **Remove Doubles**.
 
 It is not recommended to use this node if you are not going to use bmesh operations and just want to get mesh data, because it is a lot slower to create.(Object Mesh Data node can get the same data in about 33x the speed of the bmesh)
 
@@ -16,8 +16,8 @@ Inputs
 ------
 
 - **Object** - An object.
-- **Use World Space** - This option allow you to choose between local and global coordiate space for the output vectors (vertices location).
-- **Use Modifiers** - This option if enabled will return the data as modifiers were applied, that include both the generative and defomative modifiers.
+- **Use World Space** - This option allows you to choose between local and global coordiate space for the output vectors (vertices location).
+- **Use Modifiers** - This option if enabled will return the data as modifiers were applied, that includes both the generative and defomative modifiers.
 - **Scene** - `To Do`
 
 Outputs

docs/user_guide/nodes/mesh/bmesh_mesh_data.rst

@@ -3,7 +3,7 @@ Bmesh Mesh Data
 
 Description
 -----------
-This node return the mesh data of the input bmesh.
+This node returns the mesh data of the input bmesh.
 
 .. image:: images/bmesh_mesh_data_node.png
    :width: 160pt
@@ -16,17 +16,17 @@ Inputs
 Outputs
 -------
 
-- **Vertex Locations** - A vector list that include vertices locations of the input bmesh.
-- **Edge Indices** - A list of edge indices that include all the edges of the input bmesh.
-- **Polygon Indices** - A list of polygon indices that include all the polygons of the input bmesh.
+- **Vertex Locations** - A vector list that includes vertices locations of the input bmesh.
+- **Edge Indices** - A list of edge indices that includes all the edges of the input bmesh.
+- **Polygon Indices** - A list of polygon indices that includes all the polygons of the input bmesh.
 - **Vertices** - A list of vertex data for each vertex in the input bmesh. (see notes)
 - **Polygons** - A list of polygon data for each polygon in the input bmesh. (see notes)
 
 Advanced Node Settings
 ----------------------
 
 **Weighted Center** - The polygons data type carry a vector that represent the the center of the polygon.
-If this option is disabled, the center is basically the average of the vertices locations of the polygon, or in more mathematical word, The scalars of the convex combination of the vertices of the polygon are all equal and is equal to the reciprocal of the number of vertices in that polygon.
+If this option is disabled, the center is basically the average of the vertices locations of the polygon, or in more mathematical terms, The scalars of the convex combination of the vertices of the polygon are all equal and is equal to the reciprocal of the number of vertices in that polygon.
 If this option is enabled, the scalars of each vertex of the convex combination of the vertices of the polygon will be directly proportional to the length of the two edges it is connected to.
 This option solve dispersion issue, where if we had a polygon that consist of 10 vertices, 9 of them are in a small area and one of them is far away, the average ceneter will be so close to the 9 vertices and very far from the single vertex, however the weighted center will have a center at equal distance from both the single and the 9 vertices.
 
@@ -35,7 +35,7 @@ This option solve dispersion issue, where if we had a polygon that consist of 10
 Notes
 -----
 
-- **Vertices** output is a data type that carry more information about the vertex like its normal and its weight in vertex groups and you can get them using the **Vertex Info** node, so if all you want is the location of the vertices then the **Vertex Location** output is the right output for the job.And the same apply for **Polygons**.
+- **Vertices** output is a data type that carries more information about the vertex like its normal and its weight in vertex groups and you can get them using the **Vertex Info** node, so if all you want is the location of the vertices then the **Vertex Location** output is the right output for the job. The same apply for **Polygons**.
 
 Examples of Usage
 -----------------

docs/user_guide/nodes/mesh/combine_mesh_data.rst

@@ -3,17 +3,17 @@ Combine Mesh Data
 
 Description
 -----------
-This node combine individual mesh data into a mesh data block.
+This node combines individual mesh data into a mesh data block.
 
 .. image:: images/combine_mesh_data_node.png
    :width: 160pt
 
 Inputs
 ------
 
-- **Vertex Locations** - A vector list that contain the locations of the vertices of the input mesh data.
-- **Edges Indices** - An edge indices list that contain the edge information of the input mesh data.
-- **Polygons Indices** - A polygon indices list that contain the polygon information of the input mesh data.
+- **Vertex Locations** - A vector list that contains the locations of the vertices of the input mesh data.
+- **Edges Indices** - An edge indices list that contains the edge information of the input mesh data.
+- **Polygons Indices** - A polygon indices list that contains the polygon information of the input mesh data.
 
 Outputs
 -------

docs/user_guide/nodes/mesh/get_bounding_box.rst

@@ -3,9 +3,9 @@ Get Bounding Box
 
 Description
 -----------
-This node return mesh data of a cuboid that represent the bounding box of the input object.
+This node returns mesh data of a cuboid that represents the bounding box of the input object.
 
-A bounding box is a box that bound the object, that is, each face of the box is a least upper bound or greatest lower bound of a specific vertex coordinate.
+A bounding box is a box that bounds the object, that is, each face of the box is a least upper bound or greatest lower bound of a specific vertex coordinate.
 
 .. image:: images/get_bounding_box_node.png
    :width: 160pt
@@ -18,18 +18,18 @@ Inputs
 Outputs
 -------
 
-- **Vertices** - A vector list that include vertices locations of the bounding box.
-- **Edges** - A list of edge indices that include all the edges of the bounding box.
-- **Polygons** - A list of polygon indices that include all the polygons of the bounding box.
+- **Vertices** - A vector list that includes vertices locations of the bounding box.
+- **Edges** - A list of edge indices that includes all the edges of the bounding box.
+- **Polygons** - A list of polygon indices that includes all the polygons of the bounding box.
 
 Advanced Node Settings
 ----------------------
 
-- **Use World Space** - This option allow you to choose between local and global coordinate space for the bounding box.
+- **Use World Space** - This option allows you to choose between local and global coordinate space for the bounding box.
 
 Examples of Usage
 -----------------
 
 It is not every day where you would create a bounding box or visualize it. This node is useful as it actually gives you the ability to determine the maximum and minimum value of the vertex coordinates at a certain axis, and you may use it to perform normalization for instance.
 
-In other words, if I were to calculate the x coordinate of the vertex that has the highest x coordinate (The maximum x value of all vertices) I can just get the x coordinates of the vertex at index 6---It represent the intersection of the least upper bounds in all axis so its x coordinate is the maximum x and its y is the maximum y and its z is the maximum z---The same apply for the minimum but this time the vertex at index zero is sampled.
+In other words, if I were to calculate the x coordinate of the vertex that has the highest x coordinate (The maximum x value of all vertices) I can just get the x coordinates of the vertex at index 6---It represents the intersection of the least upper bounds in all axis so its x coordinate is the maximum x and its y is the maximum y and its z is the maximum z---The same applies for the minimum but this time the vertex at index zero is sampled.