The location of the chrome distillation source changed.

README.md

 # DOM Distiller
 
 DOM Distiller aims to provide a better reading experience by distilling the
 content of the page. This distilled content can then be used in a variety of
 ways.
 
 The current efforts that will be powered by DOM Distiller:
 - Reader mode: a mobile-friendly viewing mode for Chrome mobile
 
 ## How to use Reader mode on mobile Chrome
@@ skipping 171 matching lines @@
 export CHROME_SRC=/path/to/chromium/src
 export DOM_DISTILLER_DIR=/path/to/dom-distiller
 ```
 
 - Pull generated package (from ant package) into Chrome. You can use this handy
 bash-function to help with that:
 ```bash
 roll-distiller () {
   (
     (cd $DOM_DISTILLER_DIR && ant package) && \
-    rm -rf $CHROME_SRC/third_party/dom_distiller_js/package/* && \
-    cp -rf $DOM_DISTILLER_DIR/out/package/* $CHROME_SRC/third_party/dom_distiller_js/package && \
+    rm -rf $CHROME_SRC/third_party/dom_distiller_js/dist/* && \
+    cp -rf $DOM_DISTILLER_DIR/out/package/* $CHROME_SRC/third_party/dom_distiller_js/dist/ && \
     touch $CHROME_SRC/components/resources/dom_distiller_resources.grdp
   )
 }
 ```
 - From `$CHROME_SRC` run GYP to setup ninja build files using
 ```bash
 build/gyp_chromium
 ```
 
 ## Running the Chrome browser with distiller support
@@ skipping 161 matching lines @@
 If you want you can copy some of these User-Agent aliases into normal bash
 aliases for easy access later. For example, Nexus 4 would be:
 ```bash
 --user-agent="Mozilla/5.0 (Linux; Android 4.2.1; en-us; Nexus 4 Build/JOP40D) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.166 Mobile Safari/535.19"
 ```
 
 Steps 1-3 in the guide above can typically be done in a stable version of
 Chrome, whereas the rest of the steps is typically done in your own build of
 Chrome (hence the "(Re)" in step 4). Besides speed, this also facilitates
 side-by-side comparison.