Dropbox changes

Author: deploy-code-org

pegasus/data/cdo-partners.csv

@@ -136,6 +136,7 @@ ZenDesk,https://www.zendesk.com/,infrastructure,TRUE,FALSE,TRUE,
 Actua,http://www.actua.ca/,international,TRUE,TRUE,TRUE,
 Adfaber,http://adfaber.org/,international,TRUE,TRUE,TRUE,
 Almooc,http://almooc.com/,international,TRUE,TRUE,TRUE,
+Bebras Challenge,http://www.bebraschallenge.org/,international,TRUE,TRUE,TRUE,
 Cini,http://www.consorzio-cini.it/,international,TRUE,TRUE,TRUE,
 Code Club Aotearoa,http://www.codeclub.org.nz/,international,TRUE,TRUE,TRUE,
 Fundacion Sadosky,http://www.fundacionsadosky.org.ar/,international,TRUE,TRUE,TRUE,
@@ -184,7 +185,7 @@ PopCap,http://www.popcap.com/,majoruk,TRUE,FALSE,TRUE,
 Rovio,http://www.rovio.com,majoruk,TRUE,FALSE,TRUE,
 Salesforce,http://salesforce.com,majoruk,TRUE,FALSE,TRUE,
 Code Club Aotearoa,http://www.codeclub.org.nz/,nz,FALSE,FALSE,TRUE,
-CPIT,http://www.cpit.ac.nz/,nz,FALSE,FALSE,TRUE,
+CPIT,http://www.cpit.ac.nz/news-and-events/news/cpit-supports-hour-of-code?utm_source=Homepage&utm_medium=Banner&utm_campaign=ICT%20-%20Hour%20of%20Code#,nz,FALSE,FALSE,TRUE,
 Google,http://www.google.com/,nz,FALSE,FALSE,TRUE,
 Akamai,http://www.akamai.com,other,FALSE,TRUE,FALSE,
 AngelHack,http://www.angelhack.com/,other,FALSE,TRUE,FALSE,

pegasus/sites.v3/code.org/public/educate/csp/aboutTheWidgets.md

@@ -12,7 +12,7 @@ They have been created primarily as tools to explore computer science concepts.
 
 The widgets currently reside on Baker Franke's Cloud9 account for development, but will eventually be moved under the Code.org domain on Code.org's servers.
 
-All<span xmlns:dct="http://purl.org/dc/terms/" href="http://purl.org/dc/dcmitype/InteractiveResource" property="dct:title" rel="dct:type">Code.org CSP Widgets</span> by <span xmlns:cc="http://creativecommons.org/ns#" property="cc:attributionName">Baker Franke</span> are licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-nc-sa/4.0/">Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License</a>.<br>
+All <span xmlns:dct="http://purl.org/dc/terms/" href="http://purl.org/dc/dcmitype/InteractiveResource" property="dct:title" rel="dct:type">Code.org CSP Widgets</span> by <span xmlns:cc="http://creativecommons.org/ns#" property="cc:attributionName">Baker Franke</span> are licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-nc-sa/4.0/">Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License</a>.<br>
 <a rel="license" href="http://creativecommons.org/licenses/by-nc-sa/4.0/"><img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by-nc-sa/4.0/88x31.png" /></a>
 
 
@@ -29,11 +29,11 @@ Many of the widgets employed in this curriculum were originally developed at the
 
 3. In the case of the ***Sending Bits Widgets***...
 
-* Students are *actually* posting data to a remote database (Parse.com) the content of which is not montitored, and they and can more or less post any text they like.  Use with caution if you school has policies about such things. 
-* At the moment there is a limit on the number of database requests-per-second that the widget can handle.  If you or your students do things to push that limit you won't break anything (permenantly), but data will just stop flowing and you'll end up with a lot of confused students.  It is most likely that a single classroom would hit the limit during **lesson 4** the first time you use the widget.
-* Somewhat counter-intuitively the limits on the widget are not related to the amount of data posted or retrived, but the number of times students click "send" or "recv".
+	3. Students are *actually* posting data to a remote database (Parse.com) the content of which is not montitored, and they and can more or less post any text they like.  Use with caution if you school has policies about such things. 
+	3. At the moment there is a limit on the number of database requests-per-second that the widget can handle.  If you or your students do things to push that limit you won't break anything (permenantly), but data will just stop flowing and you'll end up with a lot of confused students.  It is most likely that a single classroom would hit the limit during **lesson 4** the first time you use the widget.
+	3. Somewhat counter-intuitively the limits on the widget are not related to the amount of data posted or retrived, but the number of times students click "send" or "recv".
 
-4. If you have questions about usage or would like to give feed back please do so in the [CSP Forum](https://support.code.org/hc/communities/public/topics/200138206-CS-Principles)
+4. If you have questions about usage or would like to give feedback please do so in the [CSP Forum](https://support.code.org/hc/communities/public/topics/200138206-CS-Principles)
 
 Thanks all,