Skip to content

Commit e7b6567

Browse files
author
Manika Dhiman
committed
Acrolinx suggestions
1 parent 268b5db commit e7b6567

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/databox-online/azure-stack-edge-gpu-clustering-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ Pros and cons for supported topologies are summarized as follows:
134134
| Port 3 and Port 4 use an external switch with >=10Gbps link bandwidth, Port 1 and Port 2 in the same subnet, teamed virtual switch. | Load balancing. | |
135135
| | Higher fault tolerance. | Can't be deployed in an environment with different subnets. |
136136
| | Two independent, redundant paths between nodes. | |
137-
| | Clients do not need to reconnect. | |
137+
| | Clients don't need to reconnect. | |
138138

139139
---
140140

@@ -205,7 +205,7 @@ You can manage the Azure Stack Edge cluster via the PowerShell interface of the
205205

206206
A two-node clustered device upgrade will first apply the device updates followed by the Kubernetes cluster updates. Rolling updates to device nodes ensure minimal downtime of workloads.
207207

208-
When you apply these updates via the Azure portal, you only have to start the process on one node and both the nodes are updated.For step-by-step instructions, see [Apply updates to your two-node Azure Stack Edge device](azure-stack-edge-gpu-install-update.md).
208+
When you apply these updates via the Azure portal, you only have to start the process on one node and both the nodes are updated. For step-by-step instructions, see [Apply updates to your two-node Azure Stack Edge device](azure-stack-edge-gpu-install-update.md).
209209

210210
## Billing
211211

0 commit comments

Comments
 (0)