Remove some references to 'Windows' in Linux VM architectures

docs/reference-architectures/virtual-machines-linux/multi-vm.md

@@ -119,7 +119,7 @@ The availability set makes your application more resilient to both planned and u
 * *Planned maintenance* occurs when Microsoft updates the underlying platform, sometimes causing VMs to be restarted. Azure makes sure the VMs in an availability set are not all restarted at the same time. At least one is kept running while others are restarting.
 * *Unplanned maintenance* happens if there is a hardware failure. Azure makes sure that VMs in an availability set are provisioned across more than one server rack. This helps to reduce the impact of hardware failures, network outages, power interruptions, and so on.
 
-For more information, see [Manage the availability of virtual machines][availability set]. The following video also has a good overview of availability sets: [How Do I Configure an Availability Set to Scale VMs][availability set ch9]. 
+For more information, see [Manage the availability of Linux virtual machines][availability set]. The following video also has a good overview of availability sets: [How Do I Configure an Availability Set to Scale VMs][availability set ch9]. 
 
 > [!WARNING]
 > Make sure to configure the availability set when you provision the VM. Currently, there is no way to add a Resource Manager VM to an availability set after the VM is provisioned.
@@ -171,7 +171,7 @@ A deployment for this architecture is available on [GitHub][github-folder]. It i
 
 [naming conventions]: /azure/guidance/guidance-naming-conventions
 
-[availability set]: /azure/virtual-machines/virtual-machines-windows-manage-availability
+[availability set]: /azure/virtual-machines/virtual-machines-linux-manage-availability
 [availability set ch9]: https://channel9.msdn.com/Series/Microsoft-Azure-Fundamentals-Virtual-Machines/08
 [azure-automation]: https://azure.microsoft.com/documentation/services/automation/
 [azure-cli]: /azure/virtual-machines-command-line-tools
@@ -194,5 +194,4 @@ A deployment for this architecture is available on [GitHub][github-folder]. It i
 [vmss]: /azure/virtual-machine-scale-sets/virtual-machine-scale-sets-overview
 [vmss-design]: /azure/virtual-machine-scale-sets/virtual-machine-scale-sets-design-overview
 [vmss-quickstart]: https://azure.microsoft.com/documentation/templates/?term=scale+set
-[VM-sizes]: https://azure.microsoft.com/documentation/articles/virtual-machines-windows-sizes/
 [0]: ./images/multi-vm-diagram.png "Architecture of a multi-VM solution on Azure comprising an availability set with two VMs and a load balancer"

docs/reference-architectures/virtual-machines-linux/n-tier.md

@@ -84,7 +84,7 @@ The internal load balancer distributes network traffic from the web tier to the
 
 We recommend [DataStax Enterprise][datastax] for production use, but these recommendations apply to any Cassandra edition. For more information on running DataStax in Azure, see [DataStax Enterprise Deployment Guide for Azure][cassandra-in-azure]. 
 
-Put the VMs for a Cassandra cluster in an availability set to ensure that the Cassandra replicas are distributed across multiple fault domains and upgrade domains. For more information about fault domains and upgrade domains, see [Manage the availability of virtual machines][availability-sets-manage]. 
+Put the VMs for a Cassandra cluster in an availability set to ensure that the Cassandra replicas are distributed across multiple fault domains and upgrade domains. For more information about fault domains and upgrade domains, see [Manage the availability of virtual machines][azure-availability-sets]. 
 
 Configure three fault domains (the maximum) per availability set and 18 upgrade domains per availability set. This provides the maximum number of upgrade domains that can still be distributed evenly across the fault domains.   
 
@@ -147,8 +147,7 @@ A deployment for this architecture is available on [GitHub][github-folder]. The
 [naming conventions]: /azure/guidance/guidance-naming-conventions
 
 [azure-administration]: /azure/automation/automation-intro
-[azure-availability-sets]: /azure/virtual-machines/virtual-machines-windows-manage-availability#configure-each-application-tier-into-separate-availability-sets
-[availability-sets-manage]: /azure/virtual-machines/virtual-machines-windows-manage-availability
+[azure-availability-sets]: /azure/virtual-machines/virtual-machines-linux-manage-availability
 [bastion host]: https://en.wikipedia.org/wiki/Bastion_host
 [cassandra-consistency]: http://docs.datastax.com/en/cassandra/2.0/cassandra/dml/dml_config_consistency_c.html
 [cassandra-consistency-usage]: http://medium.com/@foundev/cassandra-how-many-nodes-are-talked-to-with-quorum-also-should-i-use-it-98074e75d7d5#.b4pb4alb2

docs/reference-architectures/virtual-machines-linux/single-vm.md

@@ -53,7 +53,7 @@ Provisioning a VM in Azure involves more moving parts than just the VM itself. T
 
 ## Recommendations
 
-This architecture shows the baseline recommendations for running a Windows VM in Azure. However, we don't recommend using a single VM for mission critical workloads, because it creates a single point of failure. For higher availability, deploy multiple VMs in an [availability set][availability-set]. For more information, see [Running multiple VMs on Azure][multi-vm]. 
+This architecture shows the baseline recommendations for running a Linux VM in Azure. However, we don't recommend using a single VM for mission critical workloads, because it creates a single point of failure. For higher availability, deploy multiple VMs in an [availability set][availability-set]. For more information, see [Running multiple VMs on Azure][multi-vm]. 
 
 ### VM recommendations
 
@@ -188,10 +188,10 @@ A deployment for this architecture is available on [GitHub][github-folder]. It i
 
 
 <!-- links -->
-[multi-vm]: ../virtual-machines-windows/multi-vm.md?toc=%2fazure%2farchitecture%24virtual-machines-linux%2f/toc.json
+[multi-vm]: ../virtual-machines-linux/multi-vm.md
 [naming conventions]: ../../best-practices/naming-conventions.md
 [audit-logs]: https://azure.microsoft.com/blog/analyze-azure-audit-logs-in-powerbi-more/
-[availability-set]: /azure/virtual-machines/virtual-machines-windows-create-availability-set
+[availability-set]: /azure/virtual-machines/virtual-machines-linux-manage-availability
 [azure-cli]: /azure/virtual-machines-command-line-tools
 [azure-linux]: /azure/virtual-machines/virtual-machines-linux-azure-overview
 [azure-storage]: /azure/storage/storage-introduction
@@ -230,7 +230,7 @@ A deployment for this architecture is available on [GitHub][github-folder]. It i
 [visio-download]: http://download.microsoft.com/download/1/5/6/1569703C-0A82-4A9C-8334-F13D0DF2F472/RAs.vsdx
 [vm-disk-limits]: /azure/azure-subscription-service-limits#virtual-machine-disk-limits
 [vm-resize]: /azure/virtual-machines/virtual-machines-linux-change-vm-size
-[vm-size-tables]: /azure/virtual-machines/virtual-machines-windows-sizes#size-tables
+[vm-size-tables]: /azure/virtual-machines/virtual-machines-linux-sizes
 [vm-sla]: https://azure.microsoft.com/support/legal/sla/virtual-machines/v1_0/
 [readme]: https://github.com/mspnp/reference-architectures/blob/master/guidance-compute-single-vm
 [blocks]: https://github.com/mspnp/template-building-blocks