Merge pull request projectcalico#6895 from ctauchen/fix-footnote-links

DOCS-835: Changes footnote-style links to regular links

calico/reference/public-cloud/gce.md

@@ -1,38 +1,26 @@
 ---
 title: Google Compute Engine
-description: Methods to ensure that traffic between containers on different hosts is not dropped by GCE fabric. 
+description: Methods to ensure that traffic between containers on different hosts is not dropped by GCE fabric.
 canonical_url: '/reference/public-cloud/gce'
 ---
 
-To deploy {{site.prodname}} in [Google Compute Engine (GCE)][GCE], you must ensure
-that traffic between containers on different hosts is not dropped by the GCE
-fabric. There are a few different options for doing this depending on your
-deployment.
+To deploy {{site.prodname}} in {% include open-new-window.html text='Google Compute Engine (GCE)' url='https://cloud.google.com/compute/' %}, you must ensure that traffic between containers on different hosts is not dropped by the GCE fabric.
+There are a few different options for doing this depending on your deployment.
 
 ## IP-in-IP encapsulation
 
-Container traffic routing can be enabled by setting [IP-in-IP encapsulation][IPIP]
-and NAT outgoing on the configured {{site.prodname}} IP pools.
+Container traffic routing can be enabled by setting [IP-in-IP encapsulation]({{site.baseurl}}/networking/vxlan-ipip) and NAT outgoing on the configured {{site.prodname}} IP pools.
 
-See the [IP pool configuration reference][IPPool]
-for information on how to configure {{site.prodname}} IP pools.
+See the [IP pool configuration reference]({{site.baseurl}}/reference/resources/ippool) for information on how to configure {{site.prodname}} IP pools.
 
 ## GCE cloud routes
 
-Traffic routing in GCE can be achieved by utilizing GCE cloud routes and
-running {{site.prodname}} in policy-only mode.  Kubernetes GCE cloud provider integration
-simplifies route configuration by enabling Kubernetes to handle creating
-routes.
+Traffic routing in GCE can be achieved by utilizing GCE cloud routes and  running {{site.prodname}} in policy-only mode.
+Kubernetes GCE cloud provider integration simplifies route configuration by enabling Kubernetes to handle creating routes.
 
 ## Enabling workload-to-WAN traffic
 
-To allow {{site.prodname}} networked containers to reach resources outside of GCE,
-you must configure outgoing NAT on your [{{site.prodname}} IP pool][IPPool].
+To allow {{site.prodname}} networked containers to reach resources outside of GCE, you must configure outgoing NAT on your [{{site.prodname}} IP pool]({{site.baseurl}}/reference/resources/ippool).
 
-GCE will perform outbound NAT on any traffic which has the source address of a virtual
-machine instance.  By enabling outgoing NAT on your {{site.prodname}} IP pool, {{site.prodname}} will
-NAT any outbound traffic from the containers hosted on the virtual machine instances.
-
-[IPIP]: {{ site.baseurl }}/networking/vxlan-ipip
-[IPPool]: {{ site.baseurl }}/reference/resources/ippool
-[GCE]: https://cloud.google.com/compute/
+GCE will perform outbound NAT on any traffic which has the source address of a virtual machine instance.
+By enabling outgoing NAT on your {{site.prodname}} IP pool, {{site.prodname}} will NAT any outbound traffic from the containers hosted on the virtual machine instances.

calico/reference/public-cloud/ibm.md

@@ -4,15 +4,12 @@ description: Calico integration with IBM Cloud.
 canonical_url: '/reference/public-cloud/ibm'
 ---
 
-{{site.prodname}} is installed and configured automatically in your [IBM Cloud Kubernetes Service][IBMKUBE].  Default policies are created to protect your Kubernetes cluster, with the option to create your own policies to protect specific services.
+{{site.prodname}} is installed and configured automatically in your {% include open-new-window.html text='IBM Cloud Kubernetes Service' url='https://www.ibm.com/cloud/container-service/' %}.  Default policies are created to protect your Kubernetes cluster, with the option to create your own policies to protect specific services.
 
 ## IP-in-IP encapsulation
 
-[IP-in-IP encapsulation][IPIP] is automatically configured to only encapsulate packets traveling across subnets, and uses NAT for outgoing connections from your containers.
+[IP-in-IP encapsulation]({{site.baseurl}}/networking/vxlan-ipip) is automatically configured to only encapsulate packets traveling across subnets, and uses NAT for outgoing connections from your containers.
 
 ## Enabling workload-to-WAN traffic
 
-This is also handled automatically in the [IBM Cloud Kubernetes Service][IBMKUBE].  No additional configuration of Calico is necessary.
-
-[IPIP]: {{ site.baseurl }}/networking/vxlan-ipip
-[IBMKUBE]: https://www.ibm.com/cloud/container-service/
+This is also handled automatically in the {% include open-new-window.html text='IBM Cloud Kubernetes Service' url='https://www.ibm.com/cloud/container-service/' %}.  No additional configuration of Calico is necessary.