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.

Sign up for GitHub

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

fix typo #44

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
+1 −1
Open

fix typo #44

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1d4e840
fix typo
rotu Feb 28, 2024
a4e4258
Merge branch 'main' into patch-1
rotu Mar 22, 2024
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
2 changes: 1 addition & 1 deletion mdbook_docs/src/graph_procedures/graph_procedures.tmpl.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Graph Procedures

A __Graph Procedure__ is much like a regular Procedure, with the only difference coming in how you structure code in
the body. As its mame implies, the body of a Graph Procedure will be structured as a graph of operations. Specifically
the body. As its name implies, the body of a Graph Procedure will be structured as a graph of operations. Specifically
it is a DAG (directed-acyclic-graph) where each node in the DAG represents some isolated unit of work which may depend
on data produced by one or more other nodes and will produce its own resulting data. This structure is inherently
parallelizable as Claro can analyze the provided DAG to schedule nodes to run as soon as possible once all of the data
Expand Down