README.textile in gemcutter-0.0.8 vs README.textile in gemcutter-0.0.9

@@ -8,26 +8,10 @@
 * Create more transparent and accessible project pages
 * Enable the community to improve and enhance the site
 
 h2. Concerns
 
-*How annoying will this be to upgrade?*<br />
-The plan is to use Gemcutter as your canonical gem repository. All of the same gems that were available on RubyForge will be ready for your consumption. The gemcutter gem will hopefully make this very easy to switch over.
-
-*How can the process for publishing gems get any easier?*<br />
-Through one command- @gem push awesome-0.0.0.gem@.
-
-*Will the process change for consumers?*<br />
-No. In fact it will make their lives better: it will be easier to get to project pages with clearer information and the same data they're used to.
-
-*Why is this better than GitHub gem hosting?*<br />
-GitHub's gem system is great, but it's not the canonical source by default. The nice part is that it takes the approval process out, but the namespacing on gems makes it hard for those new to the community to determine what is the right copy to use. Also, the goals here are much different and the site as a whole can be improved over time by the community.
-
-*How can I gain access of my gem that was available through RubyForge?*<br />
-The full process is coming soon!
-
-*How can I help?*<br />
-Fork away, and read the next section! Feel free to bug qrush via a message or on FreeNode if you're interested.
+These have been moved on to the "FAQ":http://gemcutter.org/pages/faq.
 
 h2. Contributions
 
 Gemcutter has a 'commit-bit' policy, much like the Rubinius project. Submit a patch that is accepted, and you'll get full commit access to the project. Please check the wiki for more information.