changed from markdown link to html link

Author: marciocloudflare

src/content/partials/networking-services/magic-wan/third-party/alibaba-cloud.mdx

@@ -51,7 +51,7 @@ This tutorial provides information on how to connect Alibaba Cloud infrastructur
    6. **Effective Immediately**: **Yes**.
    7. **Pre-Shared Key**: This is the pre-shared key (PSK) you will have to use in the {props.productName} IPsec tunnel. If you do not specify one here, the Alibaba system will generate a random PSK for you.
 5. Go to **Advanced Settings**, and expand the **Encryption Configuration** settings.
-6. In **IKE Configurations**, select the following settings to configure the IPsec connection. These settings have to match the supported configuration parameters for [{props.productName} IPsec tunnels]({props.ipSecTunnelsUrl}):
+6. In **IKE Configurations**, select the following settings to configure the IPsec connection. These settings have to match the supported configuration parameters for <a href={props.ipSecTunnelsUrl}>{props.productName} IPsec tunnels</a>:
    1. **Version**: _ikev2_
    2. **Negotiation Mode**: _main_
    3. **Encryption Algorithm**: _aes256_
@@ -63,7 +63,7 @@ This tutorial provides information on how to connect Alibaba Cloud infrastructur
 
 ### 1. IPsec tunnels
 
-1. Follow the [Add tunnels]({props.addTunnelsUrl}) instructions to create the required IPsec tunnels with the following options:
+1. Follow the <a href={props.addTunnelsUrl}>Add tunnels</a> instructions to create the required IPsec tunnels with the following options:
    1. **Tunnel name**: Give your tunnel a descriptive name, like `Alibaba`.
    2. **Interface address**: Choose from the subnet in your Alibaba Cloud configuration. For example, if your Alibaba default configuration is `169.xx.xx.1/30`, you might want to choose `169.xx.xx.2/30` for your {props.productName} side of the IPsec tunnel.
    3. **Customer endpoint**: This is the IP address you entered for **Locali** in Alibaba's IPsec connection. For example, `47.xxx.xxx.xxx`.
@@ -74,5 +74,5 @@ This tutorial provides information on how to connect Alibaba Cloud infrastructur
 
 ### 2. Static route
 
-1. Follow the [Configure static routes]({props.configureStaticRoutesUrl}) instructions to create a static route.
+1. Follow the <a href={props.configureStaticRoutesUrl}>Configure static routes</a> instructions to create a static route.
 2. In **Prefix**, enter the IP CIDR you used to create your virtual private cloud in the Alibaba Cloud interface. In our example we used `192.168.20.0/24`.

src/content/partials/networking-services/magic-wan/third-party/aruba-edgeconnect.mdx

@@ -3,7 +3,6 @@ params:
   - productName
   - configureOverlayPolicyUrl
 ---
----
 
 import { Details } from "~/components"
 
@@ -246,7 +245,7 @@ curl --request POST \
 
 **Create an IPsec tunnel on EdgeConnect**
 
-You can create a tunnel after the Business Intent Overlay policies have been defined. Use the correct policy or service created in [configure overlay policy]({props.configureOverlayPolicyUrl}). The local IP is the local WAN interface of the EdgeConnect device, and the remote IP is the Cloudflare public IP assigned as the tunnel endpoint.
+You can create a tunnel after the Business Intent Overlay policies have been defined. Use the correct policy or service created in <a href={props.configureOverlayPolicyUrl}>configure overlay policy</a>. The local IP is the local WAN interface of the EdgeConnect device, and the remote IP is the Cloudflare public IP assigned as the tunnel endpoint.
 
 ![Modify Passthrough Tunnel dialog with General values](~/assets/images/magic-wan/third-party/aruba-edge-connect/general-modify-passthrough.png)
 

src/content/partials/networking-services/magic-wan/third-party/aws.mdx

@@ -4,7 +4,6 @@ params:
   - addTunnelsUrl
   - createAStaticRouteUrl
 ---
----
 
 This tutorial provides information and examples of how to configure IPsec VPN between Cloudflare {props.productName} with an AWS Transit Gateway.
 
@@ -72,7 +71,7 @@ After configuring the AWS transit gateway VPN connection and the tunnel as menti
 
 ### IPsec tunnels
 
-1. Refer to [Add tunnels]({props.addTunnelsUrl}) to learn how to add an IPsec tunnel. When creating your IPsec tunnel, make sure you define the following settings:
+1. Refer to <a href={props.addTunnelsUrl}>Add tunnels</a> to learn how to add an IPsec tunnel. When creating your IPsec tunnel, make sure you define the following settings:
    - **Tunnel name**: `tunnel01`
    - **Interface address**: The `/30`CIDR block enforced by AWS (first usable IP is for the AWS side). For example, `169.254.244.2`.
    - **Customer endpoint**: The IP address from AWS's VPN tunnel outside IP address. For example, `35.xx.xx.xx`.
@@ -90,7 +89,7 @@ The static route in {props.productName} should point to the appropriate virtual
 
 To create a static route:
 
-1. Refer to [Create a static route]({props.createAStaticRouteUrl}) to learn how to create one.
+1. Refer to <a href={props.createAStaticRouteUrl}>Create a static route</a> to learn how to create one.
 2. In **Prefix**, enter the subnet for your VM. For example, `192.xx.xx.xx/24`.
 3. For the **Tunnel/Next hop**, choose the IPsec tunnel you created in the previous step.
 4. Repeat the steps above for the second IPsec tunnel you created.

src/content/partials/networking-services/magic-wan/third-party/azure-virtual-wan.mdx

@@ -54,7 +54,7 @@ A VPN site represents the remote site your Azure vWAN can reach through a VPN co
 
 ### 4. Configure VPN site for Magic IPsec tunnel health checks
 
-{props.productName} uses [Tunnel Health Checks]({props.tunnelHealthChecksUrl}) to monitor whether a tunnel is available.
+{props.productName} uses <a href={props.tunnelHealthChecksUrl}>Tunnel Health Checks</a> to monitor whether a tunnel is available.
 
 Tunnel health checks make use of ICMP probes sent from the Cloudflare side of the Magic IPsec tunnel to the remote endpoint (Azure). Probes are sent from the tunnel's interface address, which you specify in two places:
 
@@ -97,9 +97,9 @@ To connect your existing VNet to your newly created vHub:
 
 When connecting your Azure vHub VPN Gateway to {props.productName}, you need to create two {props.productName} IPsec tunnels to map to the single Azure VPN Gateway Connection created above. This is because Azure VPN Gateways are deployed with two public IP addresses.
 
-1. Create an [IPsec tunnel]({props.ipsecTunnelUrl}) in the Cloudflare dashboard.
+1. Create an <a href={props.ipsecTunnelUrl}>IPsec tunnel</a> in the Cloudflare dashboard.
 2. Make sure you have the following settings:
-   1. **Interface address**: Add the upper IP address within the first `/31` subnet selected in step 4 of the Start Azure Configuration section. Refer to [Tunnel endpoints]({props.tunnelEndpointsUrl}) for more details.
+   1. **Interface address**: Add the upper IP address within the first `/31` subnet selected in step 4 of the Start Azure Configuration section. Refer to <a href={props.tunnelEndpointsUrl}>Tunnel endpoints</a> for more details.
    2. **Customer endpoint**: The first public IP associated with your Azure VPN Gateway. For example, `40.xxx.xxx.xxx`.
    3. **Cloudflare endpoint**: Use the Cloudflare anycast address you have received from your account team. This will also be the IP address corresponding to the VPN Site in Azure. For example, `162.xxx.xxx.xxx`.
    4. **Health check rate**: Medium (default).
@@ -126,7 +126,7 @@ To create a **VPN Gateway Connection**:
 1. Go to **Virtual WAN** > **Hubs** > **Your vHub** > **Connectivity** > **VPN (Site to site)** and remove the default filter **Hub association: Connected** to display the **VPN Site** created above.
 2. Check the box next to your VPN Site and select **Connect VPN sites**.
 
-Choose the following settings. These settings have been tested by Cloudflare. However, when setting up your VPN connection note that there are other configuration parameters are also technically feasible, as documented in the [Azure documentation](https://learn.microsoft.com/en-us/azure/virtual-wan/virtual-wan-ipsec) and in the [Cloudflare documentation]({props.cloudflareDocumentationUrl}).
+Choose the following settings. These settings have been tested by Cloudflare. However, when setting up your VPN connection note that there are other configuration parameters are also technically feasible, as documented in the [Azure documentation](https://learn.microsoft.com/en-us/azure/virtual-wan/virtual-wan-ipsec) and in the <a href={props.cloudflareDocumentationUrl}>Cloudflare documentation</a>.
 
 1. **PSK**: Provide the PSK generated by Cloudflare for your {props.productName} Tunnels.
 2. **Protocol**: *IKEv2*

src/content/partials/networking-services/magic-wan/third-party/azure-vpn-gateway.mdx

@@ -57,9 +57,9 @@ The time it takes for Azure to fully provision the Virtual Network Gateway depen
 
 ## Configure {props.productName}
 
-1. Create an [IPsec tunnel]({props.ipsecTunnelUrl}) in the Cloudflare dashboard.
+1. Create an <a href={props.ipsecTunnelUrl}>IPsec tunnel</a> in the Cloudflare dashboard.
 2. Make sure you have the following settings:
-   1. **Interface address**: As the Azure Local Network Gateway will only permit specifying the lower IP address in a `/31` subnet, add the upper IP address within the `/31` subnet selected in [step 2 of the Configure Azure section](#2-configure-local-network-gateway-for-magic-ipsec-tunnel-health-checks). Refer to [Tunnel endpoints]({props.tunnelEndpointsUrl}) for more details.
+   1. **Interface address**: As the Azure Local Network Gateway will only permit specifying the lower IP address in a `/31` subnet, add the upper IP address within the `/31` subnet selected in [step 2 of the Configure Azure section](#2-configure-local-network-gateway-for-magic-ipsec-tunnel-health-checks). Refer to <a href={props.tunnelEndpointsUrl}>Tunnel endpoints</a> for more details.
    2. **Customer endpoint**: The Public IP associated with your Azure Virtual Network Gateway. For example, `40.xxx.xxx.xxx`.
    3. **Cloudflare endpoint**: Use the Cloudflare anycast address you have received from your account team. This will also be the IP address corresponding to the Local Network Gateway in Azure. For example, `162.xxx.xxx.xxx`.
    4. **Health check rate**: Leave the default option (Medium) selected.
@@ -72,7 +72,7 @@ The time it takes for Azure to fully provision the Virtual Network Gateway depen
 3. If you are using the Active/Active configuration, select **Add IPsec tunnel** and repeat step 2 to create the second {props.productName} IPsec tunnel. Use the same **Cloudflare endpoint** as for the first tunnel.
 4. Select **Add Tunnels** when you are finished.
 5.The Cloudflare dashboard will show you a list of your tunnels. Edit the tunnel(s) you have created > select **Generate a new pre-shared key** > copy the generated key. If using the Active/Active configuration, select **Change to a new custom pre-shared key** on the second tunnel and use the PSK generated for the first tunnel.
-6. Create [static routes]({props.staticRoutesUrl}) for your Azure Virtual Network subnets, specifying the newly created tunnel as the next hop.
+6. Create <a href={props.staticRoutesUrl}>static routes</a> for your Azure Virtual Network subnets, specifying the newly created tunnel as the next hop.
 
 :::note
 Both tunnels in an Active/Active configuration must use the same **Cloudflare endpoint**, because an Active/Active Azure VPN connection creates two tunnels to the same remote address.
@@ -97,7 +97,7 @@ A single Cloudflare anycast address must be used in both Active/Active and Activ
 
 ### 2. Configure Local Network Gateway for Magic IPsec tunnel health checks
 
-{props.productName} uses [Tunnel Health Checks]({props.tunnelHealthChecksUrl}) to monitor whether a tunnel is available.
+{props.productName} uses <a href={props.tunnelHealthChecksUrl}>Tunnel Health Checks</a> to monitor whether a tunnel is available.
 
 Tunnel health checks make use of ICMP probes sent from the Cloudflare side of the Magic IPsec tunnel to the remote endpoint (Azure). Probes are sent from the tunnel's interface address, which you specify in two places:
 

src/content/partials/networking-services/magic-wan/third-party/fitelnet.mdx

@@ -5,7 +5,6 @@ params:
   - typeId_ipv4_addrUrl
   - configureStaticRoutesUrl
 ---
----
 
 This tutorial describes how to configure the Furukawa Electric's FITELnet F220 and F70 devices to connect to Cloudflare {props.productName} via IPsec tunnels. The use cases described in this tutorial are for both east-west (branch to branch) and north-south (Internet-bound).
 
@@ -23,16 +22,16 @@ These configurations were tested on FITELnet F220 and F70 series with the follow
 1. Go to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
 2. Go to **{props.productName}** > **Configuration**.
 3. From the **Tunnels** tab, select **Create**.
-4. For the first IPsec tunnel, ensure the following settings are defined (refer to [Add tunnels]({props.addTunnelsUrl}) for information on settings not mentioned here):
+4. For the first IPsec tunnel, ensure the following settings are defined (refer to <a href={props.addTunnelsUrl}>Add tunnels</a> for information on settings not mentioned here):
    - **Tunnel name**: `FITEL-tunnel-1`
    - **Interface address**: Enter `10.0.0.1/31` for your first tunnel.
-   - **Customer endpoint**: This setting is not required unless your router is using an IKE ID of [type `ID_IPV4_ADDR`]({props.typeId_ipv4_addrUrl}).
+   - **Customer endpoint**: This setting is not required unless your router is using an IKE ID of <a href={props.typeId_ipv4_addrUrl}>type `ID_IPV4_ADDR`</a>.
    - **Cloudflare endpoint**: The Cloudflare anycast IP assigned to you by your account team.
    - **Pre-shared key**: Create a pre-shared key for your first tunnel.
 5. For the second IPsec tunnel, make the same changes as you did for the first tunnel, and ensure these additional setting is defined:
    - **Tunnel name**: `FITEL-tunnel-2`
    - **Interface address**: Enter `10.0.0.3/31` for your second tunnel.
-   - **Customer endpoint**: This setting is not required unless your router is using an IKE ID of [type `ID_IPV4_ADDR`]({props.typeId_ipv4_addrUrl}).
+   - **Customer endpoint**: This setting is not required unless your router is using an IKE ID of <a href={props.typeId_ipv4_addrUrl}>type `ID_IPV4_ADDR`</a>.
    - **Cloudflare endpoint**: The Cloudflare anycast IP assigned to you by your account team.
    - **Pre-shared key**: Create a pre-shared key for your second tunnel.
 
@@ -179,7 +178,7 @@ To configure routes for east-west (branch to branch) connections, refer to the f
 1. Go to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
 2. Go to **{props.productName}** > **Configuration**.
 3. From the **Static Routes** tab, select **Create**.
-4. For the first route, ensure the following settings are defined (refer to [Configure static routes]({props.configureStaticRoutesUrl}) to learn about settings not mentioned here):
+4. For the first route, ensure the following settings are defined (refer to <a href={props.configureStaticRoutesUrl}>Configure static routes</a> to learn about settings not mentioned here):
 
 - **Prefix**: `192.168.0.0/24`
 - **Tunnel/Next hop**: _FITEL-tunnel-1 / 10.0.0.0_
@@ -207,7 +206,6 @@ Use the CLI to configure these settings:
 ip route 192.168.1.0 255.255.255.0 tunnel 2
 ```
 
----
 
 ## Connection test
 

src/content/partials/networking-services/magic-wan/third-party/fortinet.mdx

@@ -7,13 +7,12 @@ params:
   - configureStaticRoutesUrl
   - checkTunnelHealthInTheDashboardUrl
 ---
----
 
 import { Render } from "~/components";
 
 This tutorial provides information and examples of how to configure Cloudflare {props.productName} with IPsec tunnels in conjunction with Fortinet FortiGate firewalls.
 
-The FortiGate configuration settings presented here support [bidirectional health checks]({props.bidirectionalHealthChecksUrl}) as required by Cloudflare {props.productName}. However, they do not factor in any other traffic flows outside of the tunnel health checks. The configuration may need to be adjusted based on your current FortiGate configuration.
+The FortiGate configuration settings presented here support <a href={props.bidirectionalHealthChecksUrl}>bidirectional health checks</a> as required by Cloudflare {props.productName}. However, they do not factor in any other traffic flows outside of the tunnel health checks. The configuration may need to be adjusted based on your current FortiGate configuration.
 
 ## Testing Environment
 
@@ -39,21 +38,21 @@ Cloudflare recommends customers configure two Magic IPsec tunnels per firewall/r
 5. When creating your IPsec tunnels:
    - **Health check type**: Change to _Request_.
    - **Replay Protection**: Do not change from the default setting.
-   - Set up fields such as **Name**, **Description**, **Interface Address**, **Customer endpoint**, and **Cloudflare endpoint** with settings that work for you. Refer to [Add tunnels]({props.addTunnelsUrl}) to learn more.
+   - Set up fields such as **Name**, **Description**, **Interface Address**, **Customer endpoint**, and **Cloudflare endpoint** with settings that work for you. Refer to <a href={props.addTunnelsUrl}>Add tunnels</a> to learn more.
 
 ### Magic static routes
 
 Add two Magic static routes to define the IP address space that exists behind the Magic IPsec tunnels - one to each of the two Magic IPsec tunnels defined in the previous section.
 
-By default, the Magic static routes are defined with the priority set to `100`. Cloudflare leverages [Equal Cost Multipath Routing (ECMP)]({props.equalCostMultipathRoutingEcmpUrl}) and will load balance the traffic equally across the two tunnels. If you prefer to use an Active/Passive model, you can leave the default value for the first route set to `100`, and set the value for the second tunnel to `150` (higher value is a lower priority).
+By default, the Magic static routes are defined with the priority set to `100`. Cloudflare leverages <a href={props.equalCostMultipathRoutingEcmpUrl}>Equal Cost Multipath Routing (ECMP)</a> and will load balance the traffic equally across the two tunnels. If you prefer to use an Active/Passive model, you can leave the default value for the first route set to `100`, and set the value for the second tunnel to `150` (higher value is a lower priority).
 
 1. Go to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
 
 2. Go to **{props.productName}** > **Configuration**.
 
 3. From the **Static Routes** tab, select **Create**.
 
-4. For the first route, ensure the following settings are defined (refer to [Configure static routes]({props.configureStaticRoutesUrl}) to learn about settings not mentioned here):
+4. For the first route, ensure the following settings are defined (refer to <a href={props.configureStaticRoutesUrl}>Configure static routes</a> to learn about settings not mentioned here):
 
    - **Prefix**: Specify the [RFC1918](https://datatracker.ietf.org/doc/html/rfc1918) subnet that exists behind the first Magic IPsec tunnel you have defined in the previous section.
    - **Tunnel/Next hop**: Select your first tunnel (Tunnel 01 of 02).
@@ -439,7 +438,7 @@ end
 
 ## Monitor Cloudflare Magic IPsec tunnel health checks
 
-The Cloudflare dashboard monitors the health of all anycast tunnels on your account that route traffic from Cloudflare to your origin network. Refer to [Check tunnel health in the dashboard]({props.checkTunnelHealthInTheDashboardUrl}) for more information.
+The Cloudflare dashboard monitors the health of all anycast tunnels on your account that route traffic from Cloudflare to your origin network. Refer to <a href={props.checkTunnelHealthInTheDashboardUrl}>Check tunnel health in the dashboard</a> for more information.
 
 ## Troubleshooting