README.cross: LibO-dev -> LOdev in the mingw section

README.cross

@@ -186,8 +186,8 @@ CXX_FOR_BUILD=ccache g++
 Once you have compiled it, you may want to try to run it:
 
 $ cd /tmp
-$ tar xf <your-build-dir>/instsetoo_native/wntgcci.pro/LibreOffice_Dev/archive/install/en-US/LibO-Dev_OOO350m1_Win_x86_install-arc_en-US.tar.gz
-$ cd LibO-Dev_OOO350m1_Win_x86_install-arc_en-US/LibO-dev\ 3.5/program
+$ tar xf <your-build-dir>/instsetoo_native/wntgcci.pro/LibreOffice_Dev/archive/install/en-US/LibO-Dev_3.6.0alpha0_Win_x86_install-arc_en-US.tar.gz
+$ cd LibO-Dev_3.6.0alpha0_Win_x86_install-arc_en-US/LOdev\ 3.6/program
 $ wine soffice.exe
 
 NB. it is important to unpack somewhere low in the hierarchy structure (like
@@ -196,13 +196,13 @@ in /tmp as advised above), otherwise you'll get BerkeleyDB errors on startup.
 And if you are brave enough, you can even debug it.  First you have to add the
 URE dll's to the wine's PATH using 'wine regedit' - see
 http://www.winehq.org/docs/wineusr-guide/environment-variables, and add
-Z:\tmp\LibO-Dev_OOO350m1_Win_x86_install-arc_en-US\LibO-dev 3.5\URE\bin
+Z:\tmp\LibO-Dev_3.6.0alpha0_Win_x86_install-arc_en-US\LOdev 3.6\URE\bin
 to "Path" in My Computer->HKEY_CURRENT_USER->Environment.
 
 Then run linkoo, so that when you rebuild something, you can directly see the
 changes the next time you run it:
 
-solenv/bin/linkoo '/tmp/LibO-Dev_OOO350m1_Win_x86_install-arc_en-US/LibO-dev 3.5' <your_clone_dir>
+solenv/bin/linkoo '/tmp/LibO-Dev_3.6.0alpha0_Win_x86_install-arc_en-US/LOdev 3.6' <your_clone_dir>
 
 And start debugging: