Apply suggestions from code review

Co-authored-by: ltrouton <[email protected]>
Co-authored-by: tiny-ben-tran <[email protected]>

Author: 3 people

modules/ROOT/partials/configuration/external_plugins-premium-npm.adoc

@@ -53,9 +53,9 @@ tinymce.init({
   selector: 'textarea',
   base_url: '/tinymce', // TinyMCE location
   external_plugins: {
-    'advcode': '../../node_modules/tinymce-premium/plugins/advcode/plugin.min.js',
-    'licensekeymanager': '../../node_modules/tinymce-premium/plugins/licensekeymanager/plugin.min.js',
-    'tinycomments': '../../node_modules/tinymce-premium/plugins/tinycomments/plugin.min.js'
+    'advcode': 'tinymce-premium/plugins/advcode/plugin.min.js',
+    'licensekeymanager': 'tinymce-premium/plugins/licensekeymanager/plugin.min.js',
+    'tinycomments': 'tinymce-premium/plugins/tinycomments/plugin.min.js'
   },
   plugins: 'advcode tinycomments',
   // ... other configuration

modules/ROOT/partials/configuration/language_url.adoc

@@ -45,7 +45,7 @@ You can find and download languages link:{gettiny}/language-packages/[here].
 
 === Example: loading premium languages from `+tinymce-premium+` (NPM)
 
-When installing the `+tinymce-premium+` NPM package, each paid translation is stored in `+node_modules/tinymce-premium/langs/+`. Configure `+language_url+` to point at the desired file.
+When installing the `+tinymce-premium+` NPM package, each translation is stored in `+node_modules/tinymce-premium/langs/+`. Configure `+language_url+` to point at the desired file.
 
 .Example
 [source,js]
@@ -59,6 +59,6 @@ tinymce.init({
 
 [NOTE]
 ====
-* Ensure the `+node_modules+` directory (or a copy of the language file) is accessible to the browser. Many projects copy the required file into a public folder (such as `+/public/langs/pt_BR.js+`) during their build step and update `+language_url+` accordingly.
+* Ensure the language file is accessible in the application. Many projects copy the required file into a static assets folder (such as `+/public/langs/pt_BR.js+`) during their build step.
 * Combine this with the approaches listed in xref:ui-localization.adoc#premium-language-packs-npm[Providing premium language packs from `+tinymce-premium+`] to match the deployment strategy.
 ====

modules/ROOT/partials/configuration/skin_url.adoc

@@ -19,18 +19,18 @@ tinymce.init({
 
 === Example: loading premium skins from `+tinymce-premium+` (NPM)
 
-When installing the `+tinymce-premium+` NPM package, premium skins are stored in `+node_modules/tinymce-premium/skins/ui/+`. Configure the `+skin_url+` to point at the desired skin directory. For example:
+Configure the `+skin_url+` to point at the appropriate location. For example:
 
 [source,js]
 ----
 tinymce.init({
   selector: 'textarea',
-  skin_url: '/node_modules/tinymce-premium/skins/ui/fabric'
+  skin_url: '/<path_to_premium_skins>/ui/fabric'
 });
 ----
 
 [NOTE]
 ====
-* Ensure the `+node_modules+` directory (or a copy of the skin directory) is accessible to the browser. Many projects copy the required skin into a public folder (such as `+/public/skins/ui/oxide+`) during their build step and update `+skin_url+` accordingly.
+* Ensure the skin directory is accessible to the application. Many projects copy the required skin into a static assets folder (such as `+/public/skins/ui/oxide+`) during their build step.
 * Combine this with the approaches listed in xref:bundling-skins.adoc#premium-skins-npm[Premium skins from `+tinymce-premium+`] to match the deployment strategy.
 ====

modules/ROOT/partials/install/npm-premium-plugins-install.adoc

@@ -36,13 +36,13 @@ For information on obtaining a license key, see: xref:license-key.adoc[License K
 
 After installing `+tinymce-premium+`, you need to:
 
-* Import or configure the premium plugins (see options below)
+* Import or configure to include the premium plugins (see options below)
 * Add the plugins to your editor's `+plugins+` configuration
 * Set your commercial `+license_key+` in the editor initialization
 
 [NOTE]
 ====
-When bundling, you import individual premium plugins (e.g., `+import 'tinymce-premium/plugins/advcode'+`), not the package itself. You do **not** need `+import tinymcePremium from 'tinymce-premium'+` - only import the specific plugins you need.
+When bundling, you can only import premium plugins individually (e.g., `+import 'tinymce-premium/plugins/advcode'+`). You can **not**  include  `+import 'tinymce-premium'+` - only import the specific plugins you need.
 ====
 
 For complete examples, see the integration guides for your specific framework.

modules/ROOT/partials/integrations/angular-quick-start.adoc

@@ -130,7 +130,7 @@ import { EditorComponent, TINYMCE_SCRIPT_SRC } from '@tinymce/tinymce-angular';
 +
 [NOTE]
 ====
-When using `+TINYMCE_SCRIPT_SRC+` to lazy load TinyMCE, you cannot import premium plugins directly. Premium plugins must be bundled with your application. For instructions on bundling TinyMCE with premium plugins, see: xref:angular-pm-bundle.adoc[Bundling with Angular].
+When using `+TINYMCE_SCRIPT_SRC+` to lazy load TinyMCE, you can not import premium plugins directly. This will trigger a `tinymce not defined` error in your application because the plugins need to access `tinymce` global variable which doesn't exist at that time.
 ====
 * To load {productname} when the page or application is loaded:
 .. Open `+angular.json+` and add {productname} to the _global scripts_ tag.