Update cozy-viz README. Closes #14.

Author: gleachkr

cozy-viz/README.md

@@ -1,6 +1,6 @@
 # angr-viz
 
-This is a visualization tool for symbolic execution traces generated by hungr.
+This is a visualization tool for symbolic execution traces generated by cozy.
 You can use it to explore the tree of possible behaviors of a binary, before
 and after the application of a patch.
 
@@ -19,19 +19,21 @@ cozy's `server.py`—check the documentation for that.
 
 ### Loading Traces
 
-Once you have the application running in your browser, you need JSON exports of
-two symbolic execution traces. Some example pairs of traces are available under
-example-traces. Drag and drop one export into the left "prepatch" pane, and one
-into the right "postpatch" pane. After a moment, you should see two trees,
-representing the possible execution paths in the two traces.
+Once you have the application running in your browser, you need a JSON export
+of a comparitive symbolic execution. Example traces are available as artifacts
+from Cozy's CI builds,
+[here](https://github.com/draperlaboratory/cozy/actions/). Drag and drop the
+trace into the browser window that where you've opened cozy-viz. After
+a moment, you should see two trees, representing the possible execution paths
+in the two traces.
 
 ### Comparing Branches
 
 To compare two execution paths, you can start by mousing over nodes in the
 prepatch tree. A tooltip will let you see information associated with each
 node: blocks of assembly, logical constraints on arguments, stdout and stderr
 contents, and any error messages associated with failed states (failed states
-are highlighted in a light red color).
+are highlighted in a light red color), and potentially some other properties.
 
 Once you've found an interesting execution path in the prepatch tree, click on
 the terminal node of the path. The right tree will then highlight the branches
@@ -109,7 +111,6 @@ The basic format is:
 } 
 ```
 
-angr-viz consolidates non-branching sequences of nodes, so there are likely
-more nodes listed in the JSON that will actually appear in the visualization.
 Depending on how cozy was configured to generate the JSON, not every field
-above will necessarily appear.
+listed under `elements.nodes.data` will necessarily appear, and some fields not
+explicitly listed may occur.