Update system-requirements.md

Nick says to remove the config file example as yaml is indent sensitive and this could cause problems for customers. opted to just explain instead

Author: alt-key

articles/azure-arc/resource-bridge/system-requirements.md

@@ -116,47 +116,7 @@ Arc resource bridge uses a MOC login credential called [KVA token](/azure-stack/
 
 To use AKS and Arc resource bridge together on Azure Stack HCI, the AKS cluster must be deployed prior to deploying Arc resource bridge. If Arc resource bridge has already been deployed, AKS can't be deployed unless you delete Arc resource bridge first. Once your AKS cluster is deployed to Azure Stack HCI, you can deploy Arc resource bridge.
 
-The following example shows a network configuration setup for Arc resource bridge and AKS clusters when deployed on Azure Stack HCI. Key details are that Arc resource bridge and AKS share the same switch and `ipaddressprefix`, but require different IP addresses for `vippoolstart/end` and `k8snodeippoolstart/end`.
-
-### AKS hybrid
-
-```
-azurestackhciprovider: 
-   virtualnetwork: 
-      name: "mgmtvnet" 
-      vswitchname: "Default Switch" 
-      type: "Transparent" 
-      macpoolname:  
-      vlanid: 0 
-      ipaddressprefix: 172.16.0.0/16 
-      gateway: 17.16.1.1  
-      dnsservers: 17.16.1.1 
-      vippoolstart: 172.16.255.0 
-      vippoolend: 172.16.255.254 
-      k8snodeippoolstart: 172.16.10.0 
-      k8snodeippoolend: 172.16.10.254  
-```
-
-### Arc resource bridge
-
-```
-azurestackhciprovider: 
-   virtualnetwork: 
-      name: "mgmtvnet" 
-      vswitchname: "Default Switch" 
-      type: "Transparent" 
-      macpoolname:  
-      vlanid: 0 
-      ipaddressprefix: 172.16.0.0/16 
-      gateway: 17.16.1.1 
-      dnsservers: 17.16.0.1 
-      vippoolstart: 172.16.250.0 
-      vippoolend: 172.16.250.254 
-      k8snodeippoolstart: 172.16.30.0 
-      k8snodeippoolend: 172.16.30.254 
-```
-
-For instructions for how to deploy Arc resource bridge on Hybrid AKS, see [How to install Azure Arc Resource Bridge on Windows Server - AKS hybrid](/azure/aks/hybrid/deploy-arc-resource-bridge-windows-server). 
+When deploying Arc resource bridge with AKS on Azure Stack HCI (AKS Hybrid), the resource bridge should share the same 'vswitchname' and `ipaddressprefix`, but require different IP addresses for `vippoolstart/end` and `k8snodeippoolstart/end`. Arc resource bridge should be given a unique 'vnetname' that is different from the one used for AKS Hybrid. For full instructions to deploy Arc resource bridge on AKS Hybrid, see [How to install Azure Arc Resource Bridge on Windows Server - AKS hybrid](/azure/aks/hybrid/deploy-arc-resource-bridge-windows-server). 
 
 ## Next steps