diff --git a/docs/VLSI/Sky130-OpenROAD-Tutorial.rst b/docs/VLSI/Sky130-OpenROAD-Tutorial.rst
index 2f113f79..059412da 100644
--- a/docs/VLSI/Sky130-OpenROAD-Tutorial.rst
+++ b/docs/VLSI/Sky130-OpenROAD-Tutorial.rst
@@ -154,7 +154,10 @@ After completion, the final database can be opened in an interactive OpenROAD se
     cd ./build/par-rundir
     ./generated-scripts/open_chip
 
-TODO: insert screenshot of database here
+
+Below is the post-PnR layout for the TinyRocketConfig in Sky130 generated by OpenROAD.
+
+.. image:: ../_static/images/vlsi-openroad-par-tinyrocketconfig.png
 
 Intermediate databases are written in ``build/par-rundir`` between each step of the ``par`` action. These databases can be restored in an interactive OpenROAD session as desired for debugging purposes.
 
@@ -199,6 +202,7 @@ The below examples use the ``redo-par`` Make target to re-run only place-and-rou
       # example of re-running only floorplanning to test out a new floorplan configuration
       make redo-par HAMMER_EXTRA_ARGS="--only_step floorplan_design -p example-sky130.yml"
 
+See the `OpenROAD tool plugin README <https://github.com/ucb-bar/hammer/tree/master/src/hammer-vlsi/par/openroad>`__ for the full list of OpenROAD tool steps.
 
 Documentation
 -------------
diff --git a/docs/_static/images/vlsi-openroad-par-tinyrocketconfig.png b/docs/_static/images/vlsi-openroad-par-tinyrocketconfig.png
new file mode 100644
index 00000000..0d8ce137
Binary files /dev/null and b/docs/_static/images/vlsi-openroad-par-tinyrocketconfig.png differ