Skip to content

Commit 7fb448b

Browse files
updated language to remove passive voice
1 parent 2760dd2 commit 7fb448b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/virtual-desktop/disaster-recovery-concepts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -97,7 +97,7 @@ When using this disaster recovery strategy, it's important to keep the following
9797

9898
- Having multiple session hosts online across many regions can impact user experience. The managed network load balancer doesn't account for geographic proximity, instead treating all hosts in a host pool equally.
9999

100-
- During a disaster, the users will be creating *new* profiles in the secondary region and assumes business or mission-critical data is stored in OneDrive ([using Well-known folder redirection](/sharepoint/redirect-known-folders)) or Sharepoint. This provides users with quick access to their applications with minor disruption to the user experience.
100+
- During a disaster, users will be creating new profiles in the secondary region. You should store any business- or mission-critical data in OneDrive ([using Well-known folder redirection](/sharepoint/redirect-known-folders)) or Sharepoint. Storing data here will give users quick access to their applications with minor disruption to the user experience.
101101

102102
- Make sure that you configure your virtual machines (VMs) exactly the same way within your host pool. Also, make sure all VMs within your host pool are the same size. If your VMs aren't the same, the managed network load balancer will distribute user connections evenly across all available VMs. The smaller VMs may become resource-constrained earlier than expected compared to larger VMs, resulting in a negative user experience.
103103

0 commit comments

Comments
 (0)