Revise orchestration mode explanation in documentation

Updated orchestration mode description to emphasize flexible orchestration as the default and recommended mode for new deployments.

Author: staleycyn

learn-pr/wwl-azure/configure-virtual-machine-availability/includes/8-create-scale-sets.md

@@ -5,7 +5,7 @@ In the Azure portal, there are several settings to configure to create an Azure
 :::image type="content" source="../media/implement-scale-sets-61516afb.png" alt-text="Screenshot that shows how to create Virtual Machine Scale Sets in the Azure portal.":::
 
 
-- [**Orchestration mode**](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes): Choose how the scale set manages the virtual machines. In flexible orchestration mode, you manually create and add a virtual machine of any configuration to the scale set. In uniform orchestration mode, you define a virtual machine model and Azure generates identical instances based on that model.
+- [**Orchestration mode**](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-orchestration-modes): Choose how the scale set manages the virtual machines. Flexible orchestration is the default and recommended mode for new deployments. For most new workloads, accept the Flexible default unless you have a specific requirement for identical instances.
 
 - **Image**: Choose the base operating system or application for the VM.
 
@@ -15,4 +15,4 @@ In the Azure portal, there are several settings to configure to create an Azure
 
 Under the **Advanced** tab, you can also select the following: 
 
-- **Spreading algorithm**: The spreading algorithm determines how VMs in the scale set are balanced across fault domains. With max spreading, VMs are spread across as many fault domains as possible in each zone. With fixed spreading, VMs are always spread across exactly five fault domains. In the case where fewer than five fault domains are available, a scale set using "Max spreading" completes, while a scale set using "Fixed spreading" fails. For this reason, Microsoft recommends using **Max spreading** for your implementation. 
+- **Spreading algorithm**: The spreading algorithm determines how VMs in the scale set are balanced across fault domains. With max spreading, VMs are spread across as many fault domains as possible in each zone. With fixed spreading, VMs are always spread across exactly five fault domains. In the case where fewer than five fault domains are available, a scale set using "Max spreading" completes, while a scale set using "Fixed spreading" fails. For this reason, Microsoft recommends using **Max spreading** for your implementation.