Wording improvements in integration docs

Author: adamnsch

docs/source/integration.rst

@@ -24,15 +24,15 @@ The ``from_dfs`` method takes two mandatory positional parameters:
 
 * A Pandas ``DataFrame``, or iterable (eg. list) of DataFrames representing the nodes of the graph.
   The rows of the DataFrame(s) should represent the individual nodes, and the columns should represent the node
-  IDs and properties. The columns map directly to fields on :doc:`Nodes <./api-reference/node>`, and as such
+  IDs and properties. The columns map directly to fields of :doc:`Node <./api-reference/node>`, and as such
   should follow the same naming conventions.
 * A Pandas ``DataFrame``, or iterable (eg. list) of DataFrames representing the relationships of the graph.
   The rows of the DataFrame(s) should represent the individual relationships, and the columns should represent the
-  relationship IDs and properties. The columns map directly to fields on
-  :doc:`Relationships <./api-reference/relationship>`, and as such should follow the same naming conventions.
+  relationship IDs and properties. The columns map directly to fields of
+  :doc:`Relationship <./api-reference/relationship>`, and as such should follow the same naming conventions.
 
-``from_dfs`` also takes an optional property, ``node_radius_min_max``, can be used (and is used by default) to scale
-the node sizes for the visualization.
+``from_dfs`` also takes an optional property, ``node_radius_min_max``, that can be used (and is used by default) to
+scale the node sizes for the visualization.
 It is a tuple of two numbers, representing the radii (sizes) in pixels of the smallest and largest nodes respectively in
 the visualization.
 The node sizes will be scaled such that the smallest node will have the size of the first value, and the largest node
@@ -89,15 +89,15 @@ The ``from_gds`` method takes two mandatory positional parameters:
 * An initialized ``GraphDataScience`` object for the connection to the GDS instance, and
 * A ``Graph`` representing the projection that one wants to import.
 
-We can also provide an optional ``size_property`` parameter, which should refer to a node property of the projection, and
-will be used to determine the size of the nodes in the visualization.
+We can also provide an optional ``size_property`` parameter, which should refer to a node property of the projection,
+and will be used to determine the size of the nodes in the visualization.
 
 The ``additional_node_properties`` parameter is also optional, and should be a list of additional node properties of the
 projection that you want to include in the visualization.
 For example, these properties could be used to color the nodes, or give captions to them in the visualization.
 
-The last optional property, ``node_radius_min_max``, can be used (and is used by default) to scale the node sizes for the
-visualization.
+The last optional property, ``node_radius_min_max``, can be used (and is used by default) to scale the node sizes for
+the visualization.
 It is a tuple of two numbers, representing the radii (sizes) in pixels of the smallest and largest nodes respectively in
 the visualization.
 The node sizes will be scaled such that the smallest node will have the size of the first value, and the largest node