hardcoded magic wan for connectors

Author: marciocloudflare

src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/configure-virtual-connector.mdx

@@ -16,7 +16,6 @@ import { Render } from "~/components";
 	productNameVirtual: "Virtual Connector",
 	maintenanceURL: "/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/maintenance/",
 	dashName: "WAN Tunnels",
-	mwanName: "Magic WAN",
 	wan: "needs to correspond to the virtual network interface on the Virtual Connector instance you have set up in VMware. Following our example from the previous steps, you need to choose port `1` since that is what corresponds to the `eno1` port we set up in VMware.",
 	lan: "needs to correspond to the virtual LAN interface on the Virtual Connector instance you have set up in VMware. Following our example from the previous steps, you need to choose port `2` since that is what corresponds to the `eno2` port we set up in VMware.",
 	noConnectorShows: "For a Virtual Connector to show up you need to: <br /><ul><li><strong>VMWare:</strong> Have already obtained your OVA package and license keys if you are installing on VMWare.</li><li><strong>Proxmox:</strong> Have already obtained your Virtual Connector Script and license keys if you are installing on Proxmox.</li></ul>\nFor more information, refer to [Configure a virtual machine](#configure-a-virtual-machine) and select the appropriate tab.\n",

src/content/docs/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/reference.mdx

@@ -13,7 +13,6 @@ import { Render } from "~/components";
 	params={{
 		productName: "Magic WAN Connector",
 		dashName: "WAN Tunnels",
-		mwanName: "Magic WAN",
 		virtualProductName: "Virtual Connector",
 		gatewayURL: "/cloudflare-one/policies/gateway/",
 		hardConnectorURL: "/cloudflare-one/networks/connectors/wan-tunnels/configuration/appliances/configure-hardware-connector/",

src/content/docs/magic-wan/configuration/connector/configure-hardware-connector/index.mdx

@@ -14,7 +14,8 @@ import { Render } from "~/components";
 	magicWord: "hardware",
 	productName: "Magic WAN Connector",
 	maintenanceURL: "/magic-wan/configuration/connector/maintenance/",
-	productOriginalName: "Magic WAN",
+	dashName: "Magic WAN",
+	mwanName: "Magic WAN",
 	sfpURL: "/magic-wan/configuration/connector/configure-hardware-connector/sfp-port-information/",
 	wan: "refers to the physical Magic WAN Connector Ethernet port that you are using for your WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose the number corresponding to the port that you are using in Connector. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/magic-wan/configuration/connector/configure-hardware-connector/sfp-port-information/) for more information on the hardware supported.",
 	lan: "refers to the physical Magic WAN Connector Ethernet port that you are using for your WAN. The ports are labeled `GE1`, `GE2`, `GE3`, `GE4`, `GE5`, and `GE6`. Choose a number corresponding to the port that you are using in Connector. <br/> If you need a throughput higher than 1 Gbps, you can use one of the SFP+ ports. Refer to [SFP+ port information](/magic-wan/configuration/connector/configure-hardware-connector/sfp-port-information/) for more information on the hardware supported.",

src/content/docs/magic-wan/configuration/connector/configure-virtual-connector.mdx

@@ -15,7 +15,7 @@ import { Render } from "~/components";
 	productName: "Magic WAN Connector",
 	productNameVirtual: "Virtual Connector",
 	maintenanceURL: "/magic-wan/configuration/connector/maintenance/",
-	productOriginalName: "Magic WAN",
+	dashName: "Magic WAN",
 	wan: "needs to correspond to the virtual network interface on the Virtual Connector instance you have set up in VMware. Following our example from the previous steps, you need to choose port `1` since that is what corresponds to the `eno1` port we set up in VMware.",
 	lan: "needs to correspond to the virtual LAN interface on the Virtual Connector instance you have set up in VMware. Following our example from the previous steps, you need to choose port `2` since that is what corresponds to the `eno2` port we set up in VMware.",
 	noConnectorShows: "For a Virtual Connector to show up you need to: <br /><ul><li><strong>VMWare:</strong> Have already obtained your OVA package and license keys if you are installing on VMWare.</li><li><strong>Proxmox:</strong> Have already obtained your Virtual Connector Script and license keys if you are installing on Proxmox.</li></ul>\nFor more information, refer to [Configure a virtual machine](#configure-a-virtual-machine) and select the appropriate tab.\n",

src/content/partials/networking-services/mconn/configure-connectors.mdx

@@ -5,7 +5,6 @@ params:
   - productNameVirtual?
   - maintenanceURL
   - dashName
-  - mwanName
   - sfpURL?
   - wan
   - lan
@@ -59,7 +58,7 @@ In this page you will find instructions on how to configure {props.productName}.
 
 { props.magicWord === "hardware" && (
   <>
-		<p>You need to purchase <a href="https://www.cloudflare.com/magic-wan">{props.mwanName}</a> before you can purchase and use {props.productName}. {props.productName} can function as your primary edge device for your network, or be deployed in-line with existing network gear.</p>
+		<p>You need to purchase <a href="https://www.cloudflare.com/magic-wan">Magic WAN</a> before you can purchase and use {props.productName}. {props.productName} can function as your primary edge device for your network, or be deployed in-line with existing network gear.</p>
 
 		<p>You also need to purchase {props.productName} before you can start configuring your settings in the Cloudflare dashboard. Contact your account representative to learn more about purchasing options for {props.productName}.</p>
 
@@ -71,7 +70,7 @@ In this page you will find instructions on how to configure {props.productName}.
   <>
 		<Markdown
 		text={`
-		Before you can install ${props.productNameVirtual}, you need an Enterprise account with ${props.mwanName}. Additionally, you need to have a VMware or Proxmox host with sufficient compute, memory, and storage to run the virtual machine with ${props.productNameVirtual}. This includes:
+		Before you can install ${props.productNameVirtual}, you need an Enterprise account with Magic WAN. Additionally, you need to have a VMware or Proxmox host with sufficient compute, memory, and storage to run the virtual machine with ${props.productNameVirtual}. This includes:
     - Intel x86 CPU architecture
     - ESXi hypervisor 7.0U1 or higher
     - 4 virtual CPUs per virtual connector (We recommend deployment with a 1:1 virtual CPU to physical core allocation to avoid CPU over contention which will cause packet loss.)
@@ -325,7 +324,7 @@ You cannot enable high availability for an existing { props.magicWord === "virtu
 { props.magicWord === "hardware" && (
   <>
 		<AnchorHeading title="Register your Connector" depth={3} />
-		<p>To set up and use {props.mwanName}, you first need to register it with your account.</p>
+		<p>To set up and use Magic WAN, you first need to register it with your account.</p>
 		<Render
 			file="mconn/maintenance/register-hardware-appliance"
 			product="networking-services"
@@ -378,7 +377,7 @@ You cannot enable high availability for an existing { props.magicWord === "virtu
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
-<Render file="mconn/wan-two-tunnels" product="networking-services" params={{ productName: props.magicWord === "virtual" ? props.productNameVirtual : props.productName, dashName: props.dashName, mwanName: props.mwanName }} />
+<Render file="mconn/wan-two-tunnels" product="networking-services" params={{ productName: props.magicWord === "virtual" ? props.productNameVirtual : props.productName, dashName: props.dashName }} />
 
 1. In **WAN configuration**, select **Create**. You can create one or more [wide area networks (WANs)](https://www.cloudflare.com/learning/network-layer/what-is-a-wan/). Configuring multiple WANs will create multiple <GlossaryTooltip term="IPsec tunnel">IPsec</GlossaryTooltip> tunnels (one IPsec tunnel per WAN port). This allows { props.magicWord === "virtual" ? props.productNameVirtual : props.productName } to load balance traffic over WANs of equal priority. It also allows { props.magicWord === "virtual" ? props.productNameVirtual : props.productName } to failover between circuits according to their <GlossaryTooltip term="tunnel health-check" link={props.tunnelHealthChecksURL}>health</GlossaryTooltip>. Refer to <a href={props.wanSettingsURL}>WAN settings</a> for more details.
 		:::note

src/content/partials/networking-services/mconn/mconn-reference.mdx

@@ -2,7 +2,6 @@
 params:
   - productName
   - dashName
-  - mwanName
   - virtualProductName
   - gatewayURL
   - hardConnectorURL
@@ -96,7 +95,7 @@ When a failover occurs, traffic is moved to the new active node. It could take u
 
 This is where you add and configure your WAN connections. Each configured WAN will create one IPsec tunnel, unless you have more than one anycast IP configured in your account.
 
-<Render file="mconn/wan-two-tunnels" product="networking-services" params={{ productName: props.productName, dashName: props.dashName, mwanName: props.mwanName }} />
+<Render file="mconn/wan-two-tunnels" product="networking-services" params={{ productName: props.productName, dashName: props.dashName }} />
 
 When you have multiple WANs you can attribute different priorities to each one. Lower values mean a higher priority. This translates in {props.productName} routing traffic through the higher priority WANs or, more precisely, over the IPsec tunnels established over that interface. On the other hand, if you configure multiple WANs of equal priority, traffic will be distributed over those links through <a href={props.ecmpRoutingURL}>Equal-Cost Multi-Path (ECMP routing)</a>.
 

src/content/partials/networking-services/mconn/wan-two-tunnels.mdx

@@ -2,7 +2,6 @@
 params:
   - productName
   - dashName
-  - mwanName
 ---
 
-When you have more than one anycast IP configured in your account (set up during your {props.mwanName} onboarding), {props.productName} will automatically create at most two tunnels per WAN port. This improves reliability and performance, and requires no additional configuration on your part.
+When you have more than one anycast IP configured in your account (set up during your Magic WAN onboarding), {props.productName} will automatically create at most two tunnels per WAN port. This improves reliability and performance, and requires no additional configuration on your part.