more copy changes (#15)

markdown/open-source/commitment/oss-contributions.md

@@ -8,6 +8,6 @@ To that end, this year we are sponsoring [TADHack Global 2021](https://tadhack.c
 
 We have also sponsored other conferences in the past, including the wonderful [CommCon](https://2019.commcon.xyz/) conference in the UK (run by the awesome Dan Jenkins of [Nimble Ape](https://nimblea.pe/)), and have attended and spoken at other open-source conferences, including [SimCon](https://blog.simwood.com/2020/06/simcon4-and-something-new/).
 
-We provided a small amount of funding this year to support the openSIPS security audit via their [gofundme](https://www.gofundme.com/f/opensips-security-audit-penetration-tests) initiative.
+We provided a small amount of funding this year to help support the [openSIPS](https://www.opensips.org/) security audit via their [gofundme](https://www.gofundme.com/f/opensips-security-audit-penetration-tests) initiative.
 
 And, finally, last but not least, we tried to purchase enough yummy baked goods last year to help save the awesome [Bearkery Bakery](https://bearbakeshop.com/), which was run by one of the best people in the RTC community, [Fred Posner](https://qxork.com/).  Ultimately, we were defeated by the pandemic, but we don't regret a moment of the effort (gurgle, burp).

markdown/open-source/commitment/oss-we-make.md

@@ -11,7 +11,7 @@ We release both jambonz and drachtio under the <a href="https://github.com/jambo
 <div id="why-mit"></div>
 
 #### Why we chose the MIT License
-A few words might be in order on why we chose the MIT License, because we notice that quite often purveyors of "free as in beer" FOSS seem to be pictured by their user base as an austere sect of itinerant, karma-seeking monks who have taken a vow of poverty and wander the open source-scape doing saintly good deeds here and there - like providing free support, or adding any old feature that anyone thinks up, at any time, at no charge.  
+A few words might be in order on why we chose the MIT License, because we notice that sometimes consumers of "free as in beer" FOSS seem to picture the software providers as some sort of austere sect of itinerant, karma-seeking monks who have taken a vow of poverty and wander the open source landscape doing saintly good deeds here and there - like providing free support, or adding any old feature that anyone thinks up, at any time, at no charge.  
 
 And sometimes, the fact that software is provided at no cost seems to result in a sense on the part of the consumer (not all mind you, but some) that it must accordingly have little or no value.
 

markdown/open-source/commitment/oss-we-use.md

@@ -9,12 +9,12 @@ Building an application like jambonz requires curating a selection of the best o
 | <a href="https://drachtio.org" target="_blank">drachtio</a> | application logic and call control | <a href="https://github.com/drachtio/drachtio-srf/blob/master/LICENSE" target="_blank">MIT</a> |
 | <a href="https://github.com/sipwise/rtpengine" target="_blank">rtpengine</a> | media proxy and transcoding | <a href="https://www.gnu.org/licenses/quick-guide-gplv3.html" target="_blank">GPL v3.0</a> |
 | <a href="https://github.com/signalwire/freeswitch" target="_blank">freeswitch</a> | media server | <a href="https://github.com/signalwire/freeswitch/blob/master/LICENSE" target="_blank">MPL v1.1</a> |
-| <a href ="https://github.com/drachtio/drachtio-freeswitch-modules" target="_blank">freeswitch plugins</a> | audio integrations w/ google, AWS, others| <a href="https://github.com/drachtio/drachtio-freeswitch-modules/blob/master/LICENSE" target="_blank">MIT</a> |
-| <a href="https://www.apiban.org/" target="_blank">apiban</a> | SBC protection from bad actors |<a href="https://www.gnu.org/licenses/old-licenses/gpl-2.0.html" target="_blank">GPL v2.0</a>  |
+| <a href ="https://github.com/drachtio/drachtio-freeswitch-modules" target="_blank">freeswitch plugins</a> | audio integrations (google, AWS, others)| <a href="https://github.com/drachtio/drachtio-freeswitch-modules/blob/master/LICENSE" target="_blank">MIT</a> |
+| <a href="https://www.apiban.org/" target="_blank">apiban</a> | protection from bad SIP traffic |<a href="https://www.gnu.org/licenses/old-licenses/gpl-2.0.html" target="_blank">GPL v2.0</a>  |
 | <a href="https://expressjs.com/" target="_blank">express</a> | HTTP middleware and web framework |<a href="https://github.com/expressjs/expressjs.com/blob/gh-pages/LICENSE.md" target="_blank">Creative Commons v3.0</a>  |
 | <a href="https://nodejs.org/" target="_blank">Node.js</a> | Javascript runtime |<a href="https://github.com/nodejs/node/blob/master/LICENSE" target="_blank">MIT</a>  |
 | <a href="https://libwebsockets.org/" target="_blank">libwebsockets</a> | websockets library |<a href="https://github.com/warmcat/libwebsockets/blob/main/LICENSE" target="_blank">MIT</a>  |
-| <a href="https://www.mysql.com/" target="_blank">mysql</a> | susbcriber database |<a href=" http://oss.oracle.com/licenses/universal-foss-exception" target="_blank">GPL v2.0 with FOSS Exception</a>  |
+| <a href="https://www.mysql.com/" target="_blank">mysql</a> | provisioning database |<a href=" http://oss.oracle.com/licenses/universal-foss-exception" target="_blank">GPL v2.0 with FOSS Exception</a>  |
 | <a href="https://github.com/influxdata/telegraf" target="_blank">Telegraf</a> | metrics agent | <a href="https://github.com/influxdata/telegraf/blob/master/LICENSE" target="_blank">MIT</a> |
 | <a href="https://github.com/influxdata/influxdb" target="_blank">Influxdb</a> | time series database | <a href="https://github.com/influxdata/influxdb/blob/master/LICENSE" target="_blank">MIT</a> |
 | <a href="https://redis.io/" target="_blank">Redis</a> | key-value store | <a href="https://redis.io/topics/license" target="_blank">3-clause BSD</a> |
@@ -27,5 +27,5 @@ Building an application like jambonz requires curating a selection of the best o
 <ol class="mxs">
   <li>When using Homer (or Grafana) with the AGPL v3 license, any changes that you make to the jambonz source code <strong>are not</strong> considered a "covered work" by that license, as the two programs are not linked.<br/>TLDR: any changes you make to jambonz source code remain under the more permissive MIT license</li>
   <li><a href="https://qxip.net/" target="_blank">QXIP</a>, the creator of Homer and the <a href="https://github.com/sipcapture/HEP" target="_blank">HEP protocol</a>, also offer a non-GPL option (<a href="https://hepic.tel" target="_blank">HEPIC</a>) that is specifically designed for the needs of large-scale telcos and Communications Service Providers.  We highly recommend it to those who need a carrier-class monitoring and SIP capture solution.</li>
-  <li>If, after reading the above, you (or the company you work for) are still scared off by the AGPL v3 license, and are not interested in <a href="https://hepic.tel" target="_blank">HEPIC</a> (have you checked it out?), then know that neither Homer nor Grafana are required components of jambonz: simply don't install them, or remove if already installed.</li>
+  <li>If, after reading the above, you (or the company you work for) are still scared off by the AGPL v3 license, and are not interested in <a href="https://hepic.tel" target="_blank">HEPIC</a> (have you checked it out?), then know that neither Homer nor Grafana are required components of jambonz - simply don't install them, or remove if already installed.</li>
 </ol>

markdown/open-source/commitment/your-contributions.md

@@ -11,7 +11,7 @@ Here are some easy (i.e. no cost) ways you can contribute:
 - Have coding skills (Node.js, React, Voip/SIP, or C++)? We'd love your help as a code contributor.
 - Evangelize.  Talk the project up to your friends and business contacts. Allow us to use your success stories in our marketing materials.
 
-All of these can be really helpful in moving a project forward.
+All of these things can be really helpful in moving a project forward.
 
 There are also several easy ways you can provide direct financial support to the project:
 
@@ -24,4 +24,6 @@ Finally, we encourage you to think about supporting open-source RTC projects mor
 
 In fact, we don't think you should think of supporting open-source in a purely symmetrical fashion - e.g., "I use project A, so I should figure out how to send money to project A".  
 
-We'd encourage you to think in a more asymmetric fashion. Supporting project A is great, but if you can't manage that, perhaps you can send some of your staff to an open-source conference this year, or maybe even provide sponsorship for one.  Or maybe you can allow project A to use your experience publicly as a success story on their web site.  The point is, there are many ways to support the overall ecosystem that you are now part of. All you need to do is care.
+We'd encourage you to think asymmetrically. Supporting project A is great, but if you can't manage that, perhaps you can send some of your staff to an open-source conference this year, or maybe even provide sponsorship for one.  Or maybe you can allow project A to use your experience publicly as a success story on their web site.  The point is, there are many ways to support the overall ecosystem that you are now a part of. 
+
+All **you** need to do, is care.