Update the readme answers a bit for typos and accuracy.

README.md

@@ -12,7 +12,7 @@ This is simply a skeleton repo for a WordPress site. Use it to jump-start your W
 ## Questions & Answers
 
 **Q:** Will you accept pull requests?  
-**A:** Maybe. I made this for my own use, and thought people might find it useful. It you want to take it in a different direction and make your own customized skeleton, then just maintain your own fork.
+**A:** Maybe — if I think the change is useful. I primarily made this for my own use, and thought people might find it useful. If you want to take it in a different direction and make your own customized skeleton, then just maintain your own fork.
 
 **Q:** Why the `/shared/` symlink stuff for uploads?  
 **A:** For local development, create `/shared/` (it is ignored by Git), and have the files live there. For production, have your deploy script (Capistrano is my choice) look for symlinks pointing to `/shared/` and repoint them to some outside-the-repo location (like an NFS shared directory or something). This gives you separation between Git-managed code and uploaded files.
@@ -27,4 +27,4 @@ This is simply a skeleton repo for a WordPress site. Use it to jump-start your W
 **A:** This is for people using memcached as an object cache backend. It should be something like: `<?php return array( "server01:11211", "server02:11211" ); ?>`. Programattic generation of this file is recommended.
 
 **Q:** Does this support WordPress in multisite mode?  
-**A:** No. Not until WordPress supports WordPress-in-a-subdirectory installation for multisite. If you're a WordPress hacker who wants to help with that feature, drop me a line!
+**A:** It will, starting with WordPress 3.5 (due out in December, 2012). Earlier versions of WordPress don't support Multisite when WordPress is in a subdirectory.