OSDOCS-8012: fix attribute for microshift

microshift_networking/microshift-cni.adoc

@@ -6,16 +6,16 @@ include::_attributes/attributes-microshift.adoc[]
 
 toc::[]
 
-OVN-Kubernetes is the default networking solution for {product-title} deployments. OVN-Kubernetes is a virtualized network for pods and services that is based on Open Virtual Network (OVN). The OVN-Kubernetes Container Network Interface (CNI) plugin is the network plugin for the cluster. A cluster that uses the OVN-Kubernetes network plugin also runs Open vSwitch (OVS) on the node. OVN configures OVS on the node to implement the declared network configuration.
+OVN-Kubernetes is the default networking solution for {microshift-short} deployments. OVN-Kubernetes is a virtualized network for pods and services that is based on Open Virtual Network (OVN). The OVN-Kubernetes Container Network Interface (CNI) plugin is the network plugin for the cluster. A cluster that uses the OVN-Kubernetes network plugin also runs Open vSwitch (OVS) on the node. OVN configures OVS on the node to implement the declared network configuration.
 
 [id="microshift-network-topology_{context}"]
 == Network topology
 OVN-Kubernetes provides an overlay-based networking implementation. This overlay includes an OVS-based implementation of Service and NetworkPolicy. The overlay network uses the Geneve (Generic Network Virtualization Encapsulation) tunnel protocol. The pod maximum transmission unit (MTU) for the Geneve tunnel is set to a smaller value than the MTU of the physical interface on the host. This smaller MTU makes room for the required information that is added to the tunnel header before it is transmitted.
 
-OVS runs as a systemd service on the {product-title} node. The OVS RPM package is installed as a dependency to the `microshift-networking` RPM package. OVS is started immediately when the `microshift-networking` RPM is installed.
+OVS runs as a systemd service on the {microshift-short} node. The OVS RPM package is installed as a dependency to the `microshift-networking` RPM package. OVS is started immediately when the `microshift-networking` RPM is installed.
 
 .{product-title} network topology
-image:317_RHbM_OVN_topology_0923.png[title="{product-title} uses an overlay-based networking implementation, details follow."]
+image:317_RHbM_OVN_topology_0923.png[title="{microshift-short} uses an overlay-based networking implementation, details follow."]
 
 [id="microshift-description-ovn-logical-components_{context}"]
 === Description of the OVN logical components of the virtualized network
@@ -79,17 +79,17 @@ Networking features not available with {product-title} {product-version}:
 
 //Q: are there immutable network settings we should tell users about?
 [id="microshift-network-comps-svcs_{context}"]
-== {product-title} networking components and services
-This brief overview describes networking components and their operation in {product-title}. The `microshift-networking` RPM is a package that automatically pulls in any networking-related dependencies and systemd services to initialize networking, for example, the `microshift-ovs-init` systemd service.
+== {microshift-short} networking components and services
+This brief overview describes networking components and their operation in {microshift-short}. The `microshift-networking` RPM is a package that automatically pulls in any networking-related dependencies and systemd services to initialize networking, for example, the `microshift-ovs-init` systemd service.
 
 NetworkManager::
-NetworkManager is required to set up the initial gateway bridge on the {product-title} node. The NetworkManager and `NetworkManager-ovs` RPM packages are installed as dependencies to the `microshift-networking` RPM package, which contains the necessary configuration files. NetworkManager in {product-title} uses the `keyfile` plugin and is restarted after installation of the `microshift-networking` RPM package.
+NetworkManager is required to set up the initial gateway bridge on the {microshift-short} node. The NetworkManager and `NetworkManager-ovs` RPM packages are installed as dependencies to the `microshift-networking` RPM package, which contains the necessary configuration files. NetworkManager in {microshift-short} uses the `keyfile` plugin and is restarted after installation of the `microshift-networking` RPM package.
 
 microshift-ovs-init::
 The `microshift-ovs-init.service` is installed by the `microshift-networking` RPM package as a dependent systemd service to microshift.service. It is responsible for setting up the OVS gateway bridge.
 
 OVN containers::
-Two OVN-Kubernetes daemon sets are rendered and applied by {product-title}.
+Two OVN-Kubernetes daemon sets are rendered and applied by {microshift-short}.
 
 * *ovnkube-master*
 Includes the `northd`, `nbdb`, `sbdb` and `ovnkube-master` containers.
@@ -97,10 +97,10 @@ Includes the `northd`, `nbdb`, `sbdb` and `ovnkube-master` containers.
 * *ovnkube-node*
 The ovnkube-node includes the OVN-Controller container.
 +
-After {product-title} boots, the OVN-Kubernetes daemon sets are deployed in the `openshift-ovn-kubernetes` namespace.
+After {microshift-short} boots, the OVN-Kubernetes daemon sets are deployed in the `openshift-ovn-kubernetes` namespace.
 
 Packaging::
-OVN-Kubernetes manifests and startup logic are built into {product-title}. The systemd services and configurations included in `microshift-networking` RPM are:
+OVN-Kubernetes manifests and startup logic are built into {microshift-short}. The systemd services and configurations included in `microshift-networking` RPM are:
 
 * `/etc/NetworkManager/conf.d/microshift-nm.conf` for NetworkManager.service
 * `/etc/systemd/system/ovs-vswitchd.service.d/microshift-cpuaffinity.conf` for ovs-vswitchd.service

microshift_networking/microshift-firewall.adoc

@@ -6,12 +6,11 @@ include::_attributes/attributes-microshift.adoc[]
 
 toc::[]
 
-Firewalls are not required in {product-title}, but using a firewall can prevent undesired access to the {product-title} API.
+Firewalls are not required in {microshift-short}, but using a firewall can prevent undesired access to the {microshift-short} API.
 
 include::modules/microshift-firewall-about.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
-[id="additional-resources"]
 .Additional resources
 
 * xref:../microshift_networking/microshift-firewall.adoc#microshift-firewall-req-settings_microshift-firewall[Required firewall settings]

microshift_networking/microshift-networking-settings.adoc

@@ -6,7 +6,7 @@ include::_attributes/attributes-microshift.adoc[]
 
 toc::[]
 
-Learn how to apply networking customization and default settings to {product-title} deployments. Each node is contained to a single machine and single {product-title}, so each deployment requires individual configuration, pods, and settings.
+Learn how to apply networking customization and default settings to {microshift-short} deployments. Each node is contained to a single machine and single {microshift-short}, so each deployment requires individual configuration, pods, and settings.
 
 Cluster Administrators have several options for exposing applications that run inside a cluster to external traffic and securing network connections:
 
@@ -42,4 +42,4 @@ include::modules/microshift-mDNS.adoc[leveloffset=+1]
 [id="additional-resources_microshift-understanding-networking-settings_{context}"]
 [role="_additional-resources"]
 == Additional resources
-* xref:../microshift_release_notes/microshift-4-14-release-notes.adoc#microshift-4-14-known-issues[{product-title} {product-version} release notes --> Known issues]
+* xref:../microshift_release_notes/microshift-4-14-release-notes.adoc#microshift-4-14-known-issues[{microshift-short} {product-version} release notes --> Known issues]