Fix some typos in docs (#1394)

Author: eumiro

CONTRIBUTING.md

@@ -119,7 +119,7 @@ are no changes made to the rust code. To avoid this you can use the
 `--no-install` package if you'd like to rerun tests without recompiling.
 Note, you only want to use this flag if you recently ran Nox and there are no
 rust code (or packaged python code) changes to the repo since then. Otherwise
-the rustworkx package Nox installs in it's virtualenv will be out of date (or
+the rustworkx package Nox installs in its virtualenv will be out of date (or
 missing).
 
 Note, if you run tests outside of Nox that you can **not** run the tests from
@@ -194,8 +194,8 @@ the run finishes so you can inspect the output.
 
 #### rustworkx-core tests
 
-As rustworkx-core is a standalone rust crate with it's own public interface it
-needs it's own testing. These tests can be a combination of doc tests (embedded
+As rustworkx-core is a standalone rust crate with its own public interface it
+needs its own testing. These tests can be a combination of doc tests (embedded
 code examples in the docstrings in the rust code) or standalone tests. You
 can refer to the rust book on how to add tests:
 

README.md

@@ -58,7 +58,7 @@ environment.
 ### Installing on a platform without precompiled binaries
 
 If there are no precompiled binaries published for your system you'll have to
-build the package from source. However, to be able able to build the package
+build the package from source. However, to be able to build the package
 from the published source package you need to have Rust >= 1.70 installed (and
 also [cargo](https://doc.rust-lang.org/cargo/) which is normally included with
 rust) You can use [rustup](https://rustup.rs/) (a cross platform installer for
@@ -177,6 +177,6 @@ NetworkX usage (hence the original name).  The project was originally started
 to build a faster directed graph to use as the underlying data structure for
 the DAG at the center of
 [qiskit](https://github.com/Qiskit/qiskit/)'s transpiler. However,
-since it's initial introduction the project has grown substantially and now
+since its initial introduction the project has grown substantially and now
 covers all applications that need to work with graphs which includes
 Qiskit.

docs/source/install.rst

@@ -25,7 +25,7 @@ Installing on a platform without precompiled binaries
 -----------------------------------------------------
 
 If there are no precompiled binaries published for your system you'll have to
-build the package from source. However, to be able able to build the package from
+build the package from source. However, to be able to build the package from
 the published source package you need to have Rust >= 1.64 installed (and also
 cargo which is normally included with rust) You can use
 `rustup <https://rustup.rs/>`_ (a cross platform installer for rust) to make this

docs/source/networkx.rst

@@ -327,7 +327,7 @@ graph and matrices in other libraries. This includes ``to_numpy_matrix()``,
 adjacency matrix).
 
 However, in rustworkx there is **only** a :meth:`~rustworkx.adjacency_matrix`
-function (and it's per type variants :meth:`~rustworkx.digraph_adjacency_matrix`
+function (and its per type variants :meth:`~rustworkx.digraph_adjacency_matrix`
 and :meth:`~rustworkx.graph_adjacency_matrix`) which will return a numpy array
 of the adjacency matrix (**not** a scipy csr sparse matrix like networkx's
 function). This function is equivalent to networkx's ``to_numpy_array()``

docs/source/release_notes.rst

@@ -185,7 +185,7 @@ New Features
   :meth:`~rustworkx.PyDiGraph.insert_node_on_in_edges_multiple`, and
   :meth:`~rustworkx.PyDiGraph.insert_node_on_out_edges_multiple` were added to
   :class:`~rustworkx.PyDiGraph`. These functions are used to insert an existing
-  node in between an reference node(s) and all it's predecessors or successors.
+  node in between an reference node(s) and all its predecessors or successors.
 - Two new functions, :func:`~rustworkx.graph_dfs_edges` and
   :func:`~rustworkx.digraph_dfs_edges`, were added to get an edge list in depth
   first order from a :class:`~rustworkx.PyGraph` and
@@ -356,7 +356,7 @@ Upgrade Notes
 -------------
 
 - The :class:`~rustworkx.PyDAG` class was renamed :class:`~rustworkx.PyDiGraph`
-  to better reflect it's functionality. For backwards compatibility
+  to better reflect its functionality. For backwards compatibility
   :class:`~rustworkx.PyDAG` still exists as a Python subclass of
   :class:`~rustworkx.PyDiGraph`. No changes should be required for existing
   users.

docs/source/tutorial/dags.rst

@@ -205,7 +205,7 @@ performed is:
 
     # Equivalency matrix
     translation_matrix = {"h": ["rz(pi/2)", "sx", "rz(pi/2)"]}
-    # Insructions natively supported on target QPU
+    # Instructions natively supported on target QPU
     hardware_instructions = {"measure", "cx", "sx", "rz", "x"}
 
     # Iterate over instructions in order and replace gates outside of native

docs/source/tutorial/introduction.rst

@@ -97,7 +97,7 @@ In the above cases, we were adding nodes with a data payload of type integer (e.
 However, rustworkx doesn't place constraints on what the node data payload can
 be, so you can use more involved objects including types which are not
 `hashable <https://docs.python.org/3/glossary.html#term-hashable>`__. For
-example, we can add a node with a data payload that's a a
+example, we can add a node with a data payload that's a
 `dict <https://docs.python.org/3/library/stdtypes.html#dict>`__:
 
 .. jupyter-execute::
@@ -219,7 +219,7 @@ Modifying elements of a graph
 
 The graph classes in rustworkx also allow for in place mutation of the payloads
 for elements in the graph. For nodes you can simply use the mapping protocol to
-change the payload via it's node index. For example:
+change the payload via its node index. For example:
 
 .. jupyter-execute::
 

rustworkx-core/README.md

@@ -18,7 +18,7 @@ that offers a general purpose high performance graph library written in Rust,
 rustworkx-core is a pure rust library that offers a stable rust API for any
 downstream crate that need it.
 
-At it's core rustworkx is built on top of the
+At its core rustworkx is built on top of the
 [petgraph](https://github.com/petgraph/petgraph) library and wraps it in a
 Python layer. However, many of the algorithms (and to a lesser extent data
 structures) needed for rustworkx are not available in petgraph. For places

rustworkx/__init__.py

@@ -125,7 +125,7 @@ class PyDAG(PyDiGraph):
         ``PyDAG`` has runtime cycle detection enabled.
     :param bool multgraph: When this is set to ``False`` the created
         ``PyDAG`` object will not be a multigraph. When ``False`` if a method
-        call is made that would add parallel edges the the weight/weight from
+        call is made that would add parallel edges the weight/weight from
         that method call will be used to update the existing edge in place.
     """
 
@@ -596,7 +596,7 @@ def k_shortest_path_lengths(graph, start, k, edge_cost, goal=None):
     :param int start: The node index to find the shortest paths from
     :param int k: The kth shortest path to find the lengths of
     :param edge_cost: A python callable that will receive an edge payload and
-        return a float for the cost of that eedge
+        return a float for the cost of that edge
     :param int goal: An optional goal node index, if specified the output
         dictionary
 
@@ -732,7 +732,7 @@ def is_isomorphic_node_match(first, second, matcher, id_order=True):
         It should be the same type as the first graph.
     :param callable matcher: A python callable object that takes 2 positional
         one for each node data object. If the return of this
-        function evaluates to True then the nodes passed to it are vieded
+        function evaluates to True then the nodes passed to it are viewed
         as matching.
     :param bool id_order: If set to ``False`` this function will use a
         heuristic matching order based on [VF2]_ paper. Otherwise it will
@@ -1144,7 +1144,7 @@ def closeness_centrality(graph, wf_improved=True):
 
     The closeness centrality of a node :math:`u` is defined as the
     reciprocal of the average shortest path distance to :math:`u` over all
-    :math:`n-1` reachable nodes in the graph. In it's general form this can
+    :math:`n-1` reachable nodes in the graph. In its general form this can
     be expressed as:
 
     .. math::

src/centrality.rs

@@ -265,7 +265,7 @@ pub fn out_degree_centrality(graph: &digraph::PyDiGraph) -> PyResult<CentralityM
 ///
 /// The closeness centrality of a node :math:`u` is defined as the
 /// reciprocal of the average shortest path distance to :math:`u` over all
-/// :math:`n-1` reachable nodes in the graph. In it's general form this can
+/// :math:`n-1` reachable nodes in the graph. In its general form this can
 /// be expressed as:
 ///
 /// .. math::
@@ -313,7 +313,7 @@ pub fn graph_closeness_centrality(graph: &graph::PyGraph, wf_improved: bool) ->
 ///
 /// The closeness centrality of a node :math:`u` is defined as the
 /// reciprocal of the average shortest path distance to :math:`u` over all
-/// :math:`n-1` reachable nodes in the graph. In it's general form this can
+/// :math:`n-1` reachable nodes in the graph. In its general form this can
 /// be expressed as:
 ///
 /// .. math::