TINYDOC-3675: Correct the open source plugin count and use "open source" in place of "community" for plugins, skins, and icon packs.

modules/ROOT/pages/bundling-guide.adoc

@@ -56,9 +56,9 @@ For more information on:
 
 == Importing plugins
 
-Most plugins can be imported directly using their plugin code. The import path depends on whether the plugin is a community or premium plugin:
+Most plugins can be imported directly using their plugin code. The import path depends on whether the plugin is an open source or premium plugin:
 
-=== Community plugins
+=== Open source plugins
 
 [source,js]
 ----
@@ -129,7 +129,7 @@ Language files are optional and used for localizing the {productname} UI and plu
 
 === Core UI language files
 
-For community packages:
+For open source packages:
 
 [source,js]
 ----
@@ -149,7 +149,7 @@ Plugin language files are separate from the main UI language files. The editor's
 
 [source,js]
 ----
-// Community plugin language file
+// Open source plugin language file
 import 'tinymce/plugins/<plugincode>/langs/<language>.js';
 
 // Premium plugin language file

modules/ROOT/pages/bundling-icons.adoc

@@ -7,9 +7,9 @@
 
 Icon packs provide visual styling for {productname}'s toolbar buttons, menu items, and contextual toolbars. When bundling {productname} with a module loader, icon packs can be included to customize the editor's appearance.
 
-{productname} includes both community and premium icon packs:
+{productname} includes both open source and premium icon packs:
 
-* **Community icon packs**: Available with all {productname} installations
+* **Open source icon packs**: Available with all {productname} installations
 * **Premium icon packs**: Available with paid {productname} subscriptions
 
 The default icon pack is always required and provides the base set of icons. Additional icon packs can be bundled to extend or replace the default icons.
@@ -27,7 +27,7 @@ The following examples show how to bundle icon packs using different module synt
 |Module Syntax |Source |Example
 
 .3+|ES6+
-|npm (community)
+|npm (open source)
 a|
 [source, js]
 ----
@@ -49,7 +49,7 @@ import '../tinymce/icons/material/icons';
 ----
 
 .3+|Common JS
-|npm (community)
+|npm (open source)
 a|
 [source, js]
 ----

modules/ROOT/pages/bundling-plugins.adoc

@@ -5,11 +5,11 @@
 
 == Overview
 
-{productname} plugins can be bundled using a module bundler such as Webpack, Rollup, or Vite. This guide covers how to include both community and premium plugins in your application bundle.
+{productname} plugins can be bundled using a module bundler such as Webpack, Rollup, or Vite. This guide covers how to include both open source and premium plugins in your application bundle.
 
-{productname} includes both community and premium plugins:
+{productname} includes both open source and premium plugins:
 
-* **Community plugins**: Available with all {productname} installations
+* **Open source plugins**: Available with all {productname} installations
 * **Premium plugins**: Available with paid {productname} subscriptions via the `+tinymce-premium+` package
 
 :editorcomponent: plugin
@@ -27,7 +27,7 @@ The following examples show the syntax for including plugins in a bundle. The ex
 |Module Syntax |Source |Example
 
 .4+|ES6+
-|npm (community plugins)
+|npm (open source plugins)
 a|
 [source, js]
 ----
@@ -41,7 +41,7 @@ a|
 import 'tinymce-premium/plugins/<plugincode>';
 ----
 
-|`.zip` (community plugins)
+|`.zip` (open source plugins)
 a|
 [source, js]
 ----
@@ -56,7 +56,7 @@ import '<path_to_tinymce_premium_zip>/plugins/<plugincode>';
 ----
 
 .4+|Common JS
-|npm (community plugins)
+|npm (open source plugins)
 a|
 [source, js]
 ----
@@ -70,7 +70,7 @@ a|
 require('tinymce-premium/plugins/<plugincode>');
 ----
 
-|`.zip` (community plugins)
+|`.zip` (open source plugins)
 a|
 [source, js]
 ----
@@ -143,7 +143,7 @@ tinymce.init({
 });
 ----
 
-For complete bundling examples, see the <<premium-plugins,Premium plugins>> and <<community-plugins,Community plugins>> sections below.
+For complete bundling examples, see the <<premium-plugins,Premium plugins>> and <<open-source-plugins,Open source plugins>> sections below.
 
 [[using-external-plugins]]
 === Loading with external_plugins

modules/ROOT/pages/editor-and-features.adoc

@@ -43,7 +43,7 @@ To check the *Referer* header, open your browser's _Developer's Tools_ and open
 
 === Step 2: Load, customize and interact with {productname}
 
-There are more than 40 open source plugins that enhance the editing experience in addition to the advanced content create solutions on {cloudname}. A range of xref:basic-example.adoc[simple examples] are available. Refer to the xref:cloud-quick-start.adoc[Quick start] section for more information.
+There are 29 open source plugins that enhance the editing experience in addition to the advanced content create solutions on {cloudname}. A range of xref:basic-example.adoc[simple examples] are available. Refer to the xref:cloud-quick-start.adoc[Quick start] section for more information.
 
 === Step 3: Specifying purchased {productname} plugins and toolbar/menu items
 

modules/ROOT/pages/editor-icons.adoc

@@ -2,7 +2,7 @@
 :navtitle: Icons
 :description: Configure the editor's toolbar button and menu item icons.
 
-{productname} icons come from icon packs. {productname} includes both community and premium icon packs, but also allows integrators to add custom icons or override {productname} icons with their own.
+{productname} icons come from icon packs. {productname} includes both open source and premium icon packs, but also allows integrators to add custom icons or override {productname} icons with their own.
 
 The default icon pack is shipped with {productname} and does not require any configuration, though it must be imported when bundling for deployment: For example:
 
@@ -15,9 +15,9 @@ Replacing the default icon can be done using the `+icons+` and `+icons_url+` set
 
 == Available icon packs
 
-{productname} includes both community and premium icon packs:
+{productname} includes both open source and premium icon packs:
 
-* **Community**: `default` (always required)
+* **Open source**: `default` (always required)
 * **Premium**: `bootstrap`, `jam`, `material`, `small`, `thin` (available with paid subscriptions)
 
 For information on which icon packs work best with which skins, see: xref:enhanced-skins-and-icon-packs.adoc#icon-pack-compatibility-matrix[Icon pack compatibility matrix].

modules/ROOT/partials/module-loading/bundling-content-css-files.adoc

@@ -1,4 +1,5 @@
-== Community
+[[open-source]]
+== [[community]]Open source
 
 Default::
 ....

modules/ROOT/partials/module-loading/bundling-icon-files.adoc

@@ -1,4 +1,5 @@
-== Community icon packs
+[[open-source-icon-packs]]
+== [[community-icon-packs]]Open source icon packs
 
 These icon packs are available with all {productname} installations:
 

modules/ROOT/partials/module-loading/bundling-plugin-files.adoc

@@ -7,8 +7,8 @@ include::partial$module-loading/bundling-premium-plugins-npm.adoc[]
 
 include::partial$module-loading/admon-bundling-plugin-langs.adoc[]
 
-[[community-plugins]]
-=== Community plugins
+[[open-source-plugins]]
+=== [[community-plugins]]Open source plugins
 
 include::partial$plugin-files/plugin-file-bundling-message.adoc[]
 

modules/ROOT/partials/module-loading/bundling-premium-plugins-npm.adoc

@@ -57,5 +57,5 @@ import 'tinymce-premium/icons/premium';
 [NOTE]
 ====
 * **Icons**: The default icon pack is always required. Premium icon packs may not include all icons and are designed to fall back to the default icons when they suit the pack. Import both the default and premium icon packs, then use the xref:editor-icons.adoc[`+icons+`] option in your editor configuration to tell {productname} to also use the premium icon pack. 
-* **Skins**: Import either a community or premium skin (not both). Configure the skin using the xref:editor-skin.adoc[`+skin+`] option in your editor configuration.
+* **Skins**: Import either an open source or premium skin (not both). Configure the skin using the xref:editor-skin.adoc[`+skin+`] option in your editor configuration.
 ====

modules/ROOT/partials/module-loading/bundling-required-components.adoc

@@ -5,14 +5,14 @@ The following components are required to bundle {productname}:
 - The `silver` theme
 - The `dom` model
 - The `default` icon pack. This is always required and provides the base set of icons for all {productname} functionality. The default icons can be extended or overridden using additional icon packs.
-- A _skin_ for styling the user interface, including toolbars and menus. This can be a community, premium or custom skin.
-- A _content skin_ for styling UI features within the content such as table and image resizing. This can be a community, premium or custom skin.
+- A _skin_ for styling the user interface, including toolbars and menus. This can be an open source, premium or custom skin.
+- A _content skin_ for styling UI features within the content such as table and image resizing. This can be an open source, premium or custom skin.
 
 The global must be first, the rest can be in any order. When using premium plugins with a commercial license, the `licensekeymanager` plugin is also required.
 
 Additional components that are optional but recommended:
 
-- _Content CSS_ for styling editor content. There are community and premium style skins available, or use custom content CSS.
+- _Content CSS_ for styling editor content. There are open source and premium style skins available, or use custom content CSS.
 - Plugins to be used with the editor.
 - A custom or premium _icon pack_ to extend or override the default icons for toolbar buttons, including contextual toolbars.
 --

modules/ROOT/partials/module-loading/bundling-skin-files.adoc

@@ -1,4 +1,5 @@
-== Community Skins
+[[open-source-skins]]
+== [[community-skins]]Open source skins
 
 Default skin (oxide)::
 ....