Apply suggestions from code review

Author: ShannonLeavitt

articles/reliability/reliability-bastion.md

@@ -1,6 +1,6 @@
 ---
 title: Reliability in Azure Bastion
-description: Find out about reliability in Azure Bastion, including availability zones and mult-region deployments.
+description: Find out about reliability in Azure Bastion, including availability zones and multi-region deployments.
 author: anaharris-ms 
 ms.author: anaharris
 ms.topic: reliability-article
@@ -86,7 +86,7 @@ When you initiate an SSH or RDP session, it can be routed to an Azure Bastion in
 
 It's possible that a session might be sent to an Azure Bastion instance in an availability zone that's different from the virtual machine you're connecting to. In the following diagram, a request from the user is sent to an Azure Bastion instance in zone 2, while the virtual machine is in zone 1:
 
-:::image type="content" source="./media/reliability-bastion/bastion-cross-zone.png" alt-text="Diagram that shows Azure Bastion with three instances; a user request goes to an Azure Bastion instance in zone 2, and is sent to a virtual machine in zone 1" border="false":::
+:::image type="content" source="./media/reliability-bastion/bastion-cross-zone.png" alt-text="Diagram that shows Azure Bastion with three instances. A user request goes to an Azure Bastion instance in zone 2 and is sent to a virtual machine in zone 1." border="false":::
 
 In most scenarios, the small amount of cross-zone latency isn't significant. However, if you have unusually stringent latency requirements for your Azure Bastion workloads, you should deploy a dedicated single-zone Azure Bastion instance in the virtual machine's availability zone. However, this configuration doesn't provide zone redundancy, and we don't recommend it for most customers.