[pull] main from nodejs:main

apps/site/pages/en/blog/npm/2013-outage-postmortem.md

@@ -14,9 +14,7 @@ We know the availability and overall health of The npm Registry is paramount to
 
 The root cause of these downtime was insufficient resources: both hardware and human. This is a full post-mortem where we will be look at how npmjs.org works, what went wrong, how we changed the previous architecture of The npm Registry to fix it, as well next steps we are taking to prevent this from happening again.
 
-All of the next steps require additional expenditure from Nodejitsu: both servers and labor. This is why along with this post-mortem we are announcing our [crowdfunding campaign: scalenpm.org](https://scalenpm.org)! Our goal is to raise enough funds so that Nodejitsu can continue to run The npm Registry as a free service for _you, the community._
-
-Please take a minute now to donate at [https://scalenpm.org](https://scalenpm.org)!
+All of the next steps require additional expenditure from Nodejitsu: both servers and labor. This is why along with this post-mortem we are announcing our crowdfunding campaign! Our goal is to raise enough funds so that Nodejitsu can continue to run The npm Registry as a free service for _you, the community._
 
 ## How does npmjs.org work?
 
@@ -73,8 +71,6 @@ The npm Registry has had a 10x year. In November 2012 there were 13.5 million do
 
 _**But we need your help!**_ All of these necessary improvements require more servers, more time from Nodejitsu staff and an overall increase to what we spend maintaining the public npm registry as a free service for the Node.js community.
 
-Please take a minute now to donate at [https://scalenpm.org](https://scalenpm.org)!
-
 [browserify]: http://browserify.org/
 [dotc]: https://github.com/substack/dotc
 [npm-rubygems]: http://andrew.ghost.io/emulating-node-js-modules-in-ruby/