fix: docs build dead links

nickjiang2378 · Jun 30, 2023 · ab7bc16 · ab7bc16
1 parent 3d0287c
commit ab7bc16
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/docs/hydroflow/architecture/index.mdx b/docs/docs/hydroflow/architecture/index.mdx
@@ -78,7 +78,7 @@ convert a graph into in-out trees.
 
 Hydroflow's _Surface Syntax_ hides
 the distinction between these two layers. It offers a natural `Iterator`-like chaining syntax for building
-graphs that get parsed and compiled into a scheduled graph of one or more compiled subgraphs. Please see the [Surface Syntax](../syntax/index) docs for more information.
+graphs that get parsed and compiled into a scheduled graph of one or more compiled subgraphs. Please see the [Surface Syntax](../syntax/) docs for more information.
 
 Alternatively, the _Core API_ allows you to interact with handoffs directly at a low
 level. It doesn't provide any notion of chainable operators. You can use Rust `Iterator`s

diff --git a/docs/docs/hydroflow/syntax/index.mdx b/docs/docs/hydroflow/syntax/index.mdx
@@ -4,7 +4,7 @@ import exampleCode from '!!raw-loader!../../../../hydroflow/examples/example_syn
 # Hydroflow Surface Syntax
 The natural way to write a Hydroflow program is using the _Surface Syntax_ documented here.
 It is a chained `Iterator`-style syntax of operators built into Hydroflow that should be sufficient
-for most uses. If you want lower-level access you can work with the `Core API` documented in the [Architecture](../architecture/index) section.
+for most uses. If you want lower-level access you can work with the `Core API` documented in the [Architecture](../architecture/) section.
 
 In this chapter we go over the syntax piece by piece: how to [embed surface syntax in Rust](./surface_embedding) and how to specify [_flows_](./surface_flows), which consist of [_data sources_](./surface_data) flowing through [_operators_](./surface_ops_gen).