fiddling with the words, emphasize "community" over "existing"

community.md

@@ -1,6 +1,7 @@
 ---
 layout: default
-permalink: /existing/
+permalink: /community/
+redirect_from: /existing/
 title: Existing projects and communities
 ---
 
@@ -8,12 +9,15 @@ If you're contributing to or extending an existing project, it's almost always e
 
 Depending on how you're building on an existing project and what its license is, using the existing project's license for your own might not just be the easiest thing to do, but a condition on which your permission to build on the existing project rests: see the "same license" condition of [some licenses](/licenses/).
 
-Some communities have strong preferences for particular licenses. If you want to participate in one of these, it will be easier to use the preferred license even if you're starting a brand new project with no existing dependencies. A few examples:
+Some communities have strong preferences for particular licenses. If you want to participate in one of these, it will be easier to use the preferred license even if you're starting a brand new project with no existing dependencies. Examples:
 
 {: .bullets}
 
 * [Apache](https://www.apache.org/licenses/) requires [Apache License 2.0](/licenses/apache-2.0/)
+* [Cloud Native Computing Foundation](https://github.com/cncf/toc/blob/master/process/project_proposals.adoc) dictates [Apache License 2.0](/licenses/apache-2.0/) by default
 * [GNU](https://www.gnu.org/licenses/license-recommendations.html) recommends [GNU GPLv3](/licenses/gpl-3.0/) for most programs
-* [OpenBSD](https://www.openbsd.org/policy.html) prefers [ISC](/licenses/isc/)
+* [NPM packages](https://libraries.io/search?platforms=NPM) overwhelmingly use the [MIT](/licenses/mit/) or the very similar [ISC](/licenses/isc) licenses
+* [OpenBSD](https://www.openbsd.org/policy.html) prefers the [ISC License](/licenses/isc/)
+* [WordPress](https://wordpress.org/about/license/) plugins and themes must be [GNU GPLv2](/licenses/gpl-2.0/) (or later)
 
-Communities come in all shapes and sizes. The examples above are *very* well established. If the community you see your project as a part of doesn't have set-in-stone licensing traditions, or you don't see your project as part of any particular community, that's just fine: [make your own choice of an open source license](/).
+Communities come in all shapes and sizes, and more than one might be pertinent (e.g., [your company](https://opensource.guide/legal/#what-does-my-companys-legal-team-need-to-know)). The examples above are *very* well established. If the community you see your project as a part of doesn't have set-in-stone licensing traditions, or you don't see your project as part of any particular community, that's just fine: [make your own choice of an open source license](/).

index.html

@@ -17,13 +17,13 @@ permalink: /
   <li class="existing">
     <a href="existing">
       <span class="triptych-sprite community"></span>
-      <h3>I’m building on an existing project or community.</h3>
+      <h3>I need to work in a community.</h3>
     </a>
     <p>
-      Use the <a href="existing">existing project’s license</a> or community’s preferred license. Your project will fit right in.
+      Use the <a href="community/">license preferred by the community</a> you’re contributing to or depending on. Your project will fit right in.
     </p>
     <p>
-      If the existing project doesn’t have a license, ask its maintainers to <a href="no-permission/#for-users">add a license</a>.
+      If you have a dependency that doesn't have a license, ask its maintainers to <a href="no-permission/#for-users">add a license</a>.
     </p>
   </li>
   <li class="whatever">