diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml
index 69010e3df..ccb07f589 100644
--- a/.github/workflows/deploy.yml
+++ b/.github/workflows/deploy.yml
@@ -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
diff --git a/mdbook/src/chapter_5/chapter_5_2.md b/mdbook/src/chapter_5/chapter_5_2.md
index 5ac6fe55c..90599e6f3 100644
--- a/mdbook/src/chapter_5/chapter_5_2.md
+++ b/mdbook/src/chapter_5/chapter_5_2.md
@@ -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).