Update ccdn/README.md

Reviewed-on: HPR/hpr_documentation#11

ccdn/README.md

@@ -1,13 +1,12 @@
 # Community Content Delivery Network (CCDN)
 
-A location to track the deployment of the HPR Community Content Delivery Network, that provides a mirror network for our content.
+_A location to track the deployment of the HPR Community Content Delivery Network, that provides a mirror network for our content._
 
+## Availability of HPR Content
 
- Availability of HPR Content
+The HPR site has traditionally been run on a single instance which makes the project vulnerable. 
 
-The HPR site has been traditionally been run on a single instance, which makes the project vulnerable. 
-
-We have experienced several times where we have suffered from issues resulting from system outages, denial of service attacks, forced decommissioning, or increased costs.
+We have experienced several occasions where we have suffered downtime, resulting from system outages, denial of service attacks, forced decommissioning, or increased costs.
 
 There is a clear need to host the content in multiple geographically distributed networks to increase reliability and redundancy.
 
@@ -15,27 +14,26 @@ Applying a [Content Delivery Network](https://en.wikipedia.org/wiki/Content_deli
 
 These large vendor solutions provide free tiers, but the long term business model shows that these are not sustainable. 
 
-Additionally the algorithms used would flag behavior considered normal for HPR contributors, as suspicious and would deny them access.
+Additionally the algorithms used would flag behavior, considered normal for HPR contributors, as suspicious and would deny them access.
 
-
-# Looking to the past
+## Looking to the past
 
 At the dawn of the Internet, it was common for websites and services like DNS to be [mirrored](https://en.wikipedia.org/wiki/Mirror_site) by friends.  
 
 This was for a long time not a viable option for HPR as the quantity of Audio Content was expensive to host and transfer, and was therefore beyond what a home user could reliably serve.
 
-Over time, in some locations members of our community have access to facilities that a few years ago would have been reserved for Internet Service Providers.
+Over time, and in some locations members of our community have access to facilities that a few years ago would have been reserved for Internet Service Providers.
 
-If you are interested in helping hosting the HPR site and media, then please get in touch with _admin @ hackerpublicradio.org_
+If you are one of the fortunate people, and would like to contribute hosting of a mirror of the HPR site and media, then please get in touch with _admin @ hackerpublicradio.org_
 
 
-## Requirements for Hosting
+### Requirements for Hosting
 
 - 24/7 Home Service
 - fixed IP address
 - unlimited bandwidth
 - fast > 500mb/sec upload
-- large > 1T of storage
+- large > 3T of storage
 - permission from your ISP to run a web server
 - Contact information know to the Janitors
 - Optional: [UPS](https://en.wikipedia.org/wiki/Uninterruptible_power_supply)

developer_information.md

@@ -16,7 +16,7 @@ Some things we can change without discussion but other things we need to get inp
 
 Changes can take a long time, community approval can take several months, while other changes require a lot of work from volunteers who are focused on other priorities.
 
-We allow redistribution by releasing all our content under a [Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)](https://creativecommons.org/licenses/by-sa/4.0/). In the same vein all our code is released under [aGPLv3](https://www.gnu.org/licenses/agpl-3.0.en.html), or other [OSI approved licenses](https://opensource.org/licenses) .
+We allow redistribution by releasing all our content under a [Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)](https://creativecommons.org/licenses/by-sa/4.0/). In the same vein all our code is released under [aGPLv3](https://www.gnu.org/licenses/agpl-3.0.en.html), or other [OSI approved licenses](https://opensource.org/licenses).
 
 We do not track statistics to the detriment of our prime directive.
 
@@ -36,7 +36,7 @@ That said, we move with the times when there is a clear advantage to do so.
 
 We run up to date patched stable software.
 
-We have a long tradition of supporting and sharing hacker culture. Any identified vulnerability are fixed with credit if requested.
+We have a long tradition of supporting and sharing hacker culture. Any identified vulnerabilities are fixed with credit if requested.
 
 We use [RSS](https://www.rssboard.org/rss-specification) as a delivery mechanism, which is by default fault tolerant.
 
@@ -46,7 +46,7 @@ All our code is on [GitTea](https://repo.anhonesthost.net/HPR), please clone loc
 
 [Our database](https://hackerpublicradio.org/hpr.sql) is updated frequently, please copy locally.
 
-Our media is served from our [Community Content Delivery Network (CCDN)](https://repo.anhonesthost.net/HPR/hpr_documentation/ccdn/)
+Our media is served from our [Community Content Delivery Network (CCDN)](https://repo.anhonesthost.net/HPR/hpr_documentation/ccdn/).
 
 Bug reports, and patches are welcome from anyone without commitment.
 
@@ -61,5 +61,5 @@ In order to contribute you need to [create an account](https://repo.anhonesthost
 Once you have set up your account, you will need to set up your local
 development environment. [Instructions here](set-up-development-environment.md)
 
-Changes can be submittted as described in [hpr3797 :: How to submit changes to HPR](https://hackerpublicradio.org/eps/hpr3797/index.html).
+Changes can be submitted as described in [hpr3797 :: How to submit changes to HPR](https://hackerpublicradio.org/eps/hpr3797/index.html).