diff --git a/fedostree/web/partials/home.html b/fedostree/web/partials/home.html
index 225b115a..8d50a280 100644
--- a/fedostree/web/partials/home.html
+++ b/fedostree/web/partials/home.html
@@ -158,9 +158,17 @@
   </p>
   <p>
     The problem is making this sort of thing efficient and scalable;
-    it would require careful integration of the local OSTree repository
-    and the package manager caching to operate at a speed comparable to
-    traditional package management.
+    it would require careful integration of the local OSTree
+    repository and the package manager caching to operate at a speed
+    comparable to traditional package management.</p>
+  <p>There are two primary issues.  First, OSTree mandates that the
+    running tree be immutable, and requires construction of a new
+    tree.  This is just a deep mismatch with how package managers are
+    built.  Second, current package managers are totally unaware of
+    the existence of the OSTree repository at /ostree/repo which holds
+    binaries.  A naive implementation would just redownload the packages,
+    which would be quite slow.
+  </p>
   </p>
   <h3>Development area: Live updates</h3>
   <p>
diff --git a/fedostree/web/partials/installation.html b/fedostree/web/partials/installation.html
index 206101af..0a9a6854 100644
--- a/fedostree/web/partials/installation.html
+++ b/fedostree/web/partials/installation.html
@@ -95,8 +95,9 @@
 <pre>
 	ostree admin upgrade
 </pre>
-  <p>Although <tt>yum</tt> is installed, it will operate in read-only mode.  Do
-     not attempt to use it at the moment.  See </p>
+  <p>Although <tt>yum</tt> is installed, it will operate in read-only
+     mode.  Do not attempt to use it at the moment.  See the section
+     on the homepage "Development area: Local package assembly".</p>
 
   <p>But with OSTree, it's possible to atomically transition between
     different complete bootable filesystem trees.  Let's now try the