Skip to content

Commit 22e5b80

Browse files
authored
Update troubleshoot-dns-load-balancing.md
Minor tweaks.
1 parent 7ba9a76 commit 22e5b80

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

support/azure/kubernetes-fleet/networking/troubleshoot-dns-load-balancing.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ This article provides troubleshooting information for Azure Kubernetes Fleet Man
2929
3030
This section provides common reasons and solutions for scenarios in which the `TrafficManagerProfile` Kubernetes object and its associated Azure Traffic Manager resource aren't created.
3131
32-
To determine the appropriate resolution, check the status of the `TrafficManagerProfile` object on the Fleet Manager hub cluster for the error message.
32+
To determine the appropriate resolution, check the status of the `TrafficManagerProfile` object on the Fleet Manager hub cluster using the shown command.
3333
3434
```bash
3535
kubectl get trafficmanagerprofile -n <namespace> <profile-name> -o yaml
@@ -124,7 +124,7 @@ Consider deleting unused profiles or requesting an increase in the limit. For mo
124124

125125
### Error 4: Azure Traffic Manager returns an error
126126

127-
This issue might occur if the Azure Traffic Manager service returns an error when it creats the profile.
127+
This issue might occur if the Azure Traffic Manager service returns an error when it creates the profile.
128128

129129
The following example of the `TrafficManagerProfile` status shows this error:
130130

@@ -147,7 +147,7 @@ If the error persists, check the Azure Traffic Manager service health.
147147

148148
This section provides common causes and recommended solutions for scenarios in which the `TrafficManagerBackend` Kubernetes object can't be created.
149149

150-
To determine the appropriate resolution, check the status of the `TrafficManagerBackend` object on the Fleet Manager hub cluster for the following error message:
150+
To determine the appropriate resolution, check the status of the `TrafficManagerBackend` object on the Fleet Manager hub cluster using the shown command.
151151

152152
```bash
153153
kubectl get trafficmanagerbackend -n <namespace> <backend-name> -o yaml

0 commit comments

Comments
 (0)