diff --git a/Lausanne-Sprint-Notes.md b/Lausanne-Sprint-Notes.md
index a58ae52..eba5566 100644
--- a/Lausanne-Sprint-Notes.md
+++ b/Lausanne-Sprint-Notes.md
@@ -1,42 +1,27 @@
-## Deliverable 1
+## March 3rd
+
+### Discussion about Deliverable 1 items
 
 * Animation - Functionally complete.  Need to have some discussion about animating the view or otherwise allowing multiple maps to share animated state.
-
 * Kinetic Panning - Complete.  Potentially some discussion needed on having other interactions stop animation.
-
 * DOM Renderer Refactoring - Complete.  This could be made to work in non CSS3 environments.  Look into reverting to old rescaling logic.
-
 * View Extraction - Complete.  Some discussion on usability needed (have map act as user convenience layer?).
-
 * Tile Queue - Complete.  Confirm tile events are properly handled.
-
 * WMTS - Source in progress.  Capabilities parsing complete.  Source needs to be configured with parsed caps structure.
-
 * Single Image WMS - Complete.  Issue with empty strings (e.g. `{style: ''}`).
-
 * Vector Architecture - Discussion on merging.
-
 * Arg Parser / Permalink - Put together a state provider instead.  Serialization to URL done at application level.
-
 * Attribution Control - Complete.  Some work for vector layer.
-
 * Mouse Position - Complete.
-
 * Mouse/Touch Navigation - Mouse handling complete.  Touch enhancements need review/merging.  Ongoing work on mousewheel handling.
-
 * Zoom Slider - Make sure we can work with other widget frameworks first (right events and interaction w/ view).
-
 * Scale Line - Additional work needed calculate point resolution for all projections.  Nearly ready for review/merge.
-
 * Zoom Control - Complete.  Check double-click handling.
-
 * Zoom to Max Extent - Allow user to position arbitrary element.  Discuss providing convenient collections with different alignment (e.g. top-left horizontal, bottom-right horizontal).
-
 * Data Source / Layer Architecture - Complete.  Review tile source v. image source.
-
 * Aggregate Layer - Need to review requirements and existing art.
 
-## Usability Discussion
+### Usability Discussion
 
 * Improve dev/build story for application developers.
 * Provide ol event registration API.  Perhaps entirely homegrown event system.