Merge pull request #292605 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/azure-resource-manager/bicep/quickstart-create-bicep-use-visual-studio-code.md

@@ -186,7 +186,7 @@ param location string = resourceGroup().location
 
 resource virtualNetwork 'Microsoft.Network/virtualNetworks@2024-03-01' = {
   name: 'exampleVNet'
-  location: resourceGroup().location
+  location: location
   properties: {
     addressSpace: {
       addressPrefixes: [
@@ -212,7 +212,7 @@ resource virtualNetwork 'Microsoft.Network/virtualNetworks@2024-03-01' = {
 
 resource exampleStorage 'Microsoft.Storage/storageAccounts@2023-05-01' = {
   name: storageAccountName
-  location: 'eastus'
+  location: location
   sku: {
     name: 'Standard_LRS'
   }

articles/load-balancer/load-balancer-floating-ip.md

@@ -70,7 +70,7 @@ The Floating IP rule type is the foundation of several load balancer configurati
 In order to function, you configure the Guest OS for the virtual machine to receive all traffic bound for the frontend IP and port of the load balancer. Configuring the VM requires:
 * adding a loopback network interface
 * configuring the loopback with the frontend IP address of the load balancer
-* ensuring the system can send/receive packets on interfaces that don't have the IP address assigned to that interface.Windows systems require setting interfaces to use the "weak host" model. For Linux systems, this model is normally used by default.
+* ensuring the system can send/receive packets on interfaces that don't have the IP address assigned to that interface. Windows systems require setting interfaces to use the "weak host" model. For Linux systems, this model is normally used by default.
 * configuring the host firewall to allow traffic on the frontend IP port.
 
 > [!NOTE]