Skip to content

Commit

Permalink
Follow header Title Case convention in mdbook (#366)
Browse files Browse the repository at this point in the history
* Follow header Title Case convention in mdbook

This is to test the new CI workflows.

* Check out code in deploy flow
  • Loading branch information
benesch committed Feb 19, 2021
1 parent 935b7e9 commit b3e3297
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 1 deletion.
1 change: 1 addition & 0 deletions .github/workflows/deploy.yml
Expand Up @@ -9,6 +9,7 @@ jobs:
deploy:
runs-on: ubuntu-20.04
steps:
- uses: actions/checkout@v2
- run: cargo install mdbook --version 0.4.6
- run: cd mdbook && mdbook build
- uses: JamesIves/github-pages-deploy-action@4.0.0
Expand Down
2 changes: 1 addition & 1 deletion mdbook/src/chapter_5/chapter_5_2.md
Expand Up @@ -14,7 +14,7 @@ Timely dataflow computations are structured so that to send a timestamped messag

Before we get into these two aspects, we will first need to be able to name parts of our dataflow graph.

## Dataflow structure
## Dataflow Structure

A dataflow graph hosts some number of operators. For progress tracking, these operators are simply identified by their index. Each operator has some number of *input ports*, and some number of *output ports*. The dataflow operators are connected by connecting each input port to a single output port (typically of another operator). Each output port may be connected to multiple distinct input ports (a message produced at an output port is to be delivered to all attached input ports).

Expand Down

0 comments on commit b3e3297

Please sign in to comment.