Add frontend plugn wiring section

Author: GitHub Actions

assemblies/dynamic-plugins/assembly-frontend-plugin-wiring.adoc renamed to assemblies/dynamic-plugins/assembly-front-end-plugin-wiring.adoc

@@ -1,8 +1,8 @@
-[id="assembly-frontend-plugin-wiring_{context}"]
-= Frontend plugin wiring
-:context: assembly-frontend-plugin-wiring
+[id="assembly-front-end-plugin-wiring_{context}"]
+= Front-end plugin wiring
+:context: assembly-front-end-plugin-wiring
 
-You can configure frontend plugins to do the following:
+You can configure front-end plugins to do the following:
 
 * Extend the internal library of available icons
 * Declare a new full page by defining a new route

modules/dynamic-plugins/proc-customizing-and-extending-entity-tabs.adoc

@@ -39,7 +39,7 @@ plugins:
 <3> The base mount point name that is available on the tab. This name is expanded to create two mount points per tab, one appended with` /context` and the second appended with `/cards`.
 <4> Specify the order of tabs. The tabs with higher priority values appear first.
 
-You can configure dynamic frontend plugins to target the mount points exposed by the entityTabs configuration. The following are the default catalog entity routes in the default order:
+You can configure dynamic front-end plugins to target the mount points exposed by the entityTabs configuration. The following are the default catalog entity routes in the default order:
 
 .Input parameters
 [cols="20%,20%,30%,30%", frame="all", options="header"]

modules/dynamic-plugins/proc-provide-additional-utility-apis.adoc

@@ -2,7 +2,7 @@
 
 = Provide additional utility APIs
 
-If a dynamic plugin exports the plugin object returned by `createPlugin`, it is supplied to the `createApp` API. All API factories exported by the plugin are automatically registered and available in the frontend application.
+If a dynamic plugin exports the plugin object returned by `createPlugin`, it is supplied to the `createApp` API. All API factories exported by the plugin are automatically registered and available in the front-end application.
 
 You can add an entry to the `dynamicPlugins.frontend` configuration when a dynamic plugin contains only API factories as shown in the following example:
 

modules/dynamic-plugins/proc-provide-custom-techdocs-addons.adoc

@@ -3,7 +3,7 @@
 = Provide custom TechDocs addons
 
 If a plugin provides multiple addons, each `techdocsAddon` entry specifies a unique `importName` corresponding to the addon.
-Frontend plugins contribute to TechDocs component, as a result, exposing the TechDocs addon component using the `techdocsAddons` configuration as shown in the following example:
+Front-end plugins contribute to TechDocs component, as a result, exposing the TechDocs addon component using the `techdocsAddons` configuration as shown in the following example:
 
 [source,yaml]
 ----

titles/plugins-rhdh-install/master.adoc

@@ -24,4 +24,4 @@ include::modules/dynamic-plugins/proc-enable-plugins-rhdh-container-image.adoc[l
 include::assemblies/dynamic-plugins/assembly-extensions-plugins.adoc[leveloffset=+1]
 
 // frontend plugin wiring
-include::assemblies/dynamic-plugins/assembly-frontend-plugin-wiring.adoc[leveloffset=+1]
+include::assemblies/dynamic-plugins/assembly-front-end-plugin-wiring.adoc[leveloffset=+1]