Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: small typo fixes #1112

Merged
merged 3 commits into from
Feb 23, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/source/networkx.rst
Original file line number Diff line number Diff line change
Expand Up @@ -95,7 +95,7 @@ or more concisely::
The other large difference to keep in mind is that many functions in rustworkx
are explicitly typed. This means that they either always return or accept
either a :class:`~rustworkx.PyDiGraph` or a :class:`~rustworkx.PyGraph` but not
both. Generally, functions prefixed with `graph_*` and `digraph_*` explicitly typed.
both. Generally, functions prefixed with `graph_*` and `digraph_*` are explicitly typed.
Explicitly typed functions also indicate their type on the docstrings.
This is different from networkx where everything is pretty much dynamically
typed and you can pass a graph object to any function and it will work as
Expand Down Expand Up @@ -137,7 +137,7 @@ networkx has a concept of
`graph <https://networkx.org/documentation/stable/tutorial.html#graph-attributes>`__,
`node <https://networkx.org/documentation/stable/tutorial.html#node-attributes>`__,
and `edge attributes <https://networkx.org/documentation/stable/tutorial.html#edge-attributes>`__
in addition to the hashable object used for a node's payload. Retworkx has
in addition to the hashable object used for a node's payload. Rustworkx has
graph attributes similar to NetworkX however instead of being treated like
a dictionary on the graph object itself they're accessible from a dedicated
:class:`~.PyGraph.attrs` attribute. This attribute can be any Python object
Expand Down
Loading