Move Version Assembly code out of chrome_elf.

chrome/app/version_assembly/README

Index: chrome/app/version_assembly/README
diff --git a/chrome_elf/README b/chrome/app/version_assembly/README
similarity index 58%
rename from chrome_elf/README
rename to chrome/app/version_assembly/README
index b657437375641fe34d6e97393f8208006489bc8c..082eaa7ba2f4eabbd78d16dc950942df7798962f 100644
--- a/chrome_elf/README
+++ b/chrome/app/version_assembly/README
@@ -1,9 +1,10 @@
-Chrome Early Loading Framework (aka ChromeELF)
+Chrome Version Assembly
 
-chrome_elf.dll is shipped in Chrome's version directory to ease updates,
-and is loaded early in chrome.exe's lifetime. This is done by turning the
-version directory into a private assembly which refers to chrome_elf.dll
-(http://msdn.microsoft.com/library/aa374224.aspx).
+The chrome version assembly makes it possible for load-time dependencies of
+chrome.exe to be shipped in Chrome's version directory to ease updates (eg.
+chrome_elf.dll). This is done by turning the version directory into a private
+assembly which refers to any DLLs that chrome.exe needs to know about. New DLLs
+should be added as <file> entries in "version_assembly_manifest.template".
 
 In an ideal world, this would be done by embedding an application config in
 chrome.exe that would refer to the proper version directory via a