Skip to content

Commit 6c0d2c7

Browse files
authored
Apply suggestions from PR review
Because you maintained the step numbers in the headings, the additional numbering here is unnecessary and might be confusing.
1 parent c0e642d commit 6c0d2c7

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/application-gateway/for-containers/migrate-from-agic-to-agc.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -82,10 +82,10 @@ Here's a summarized list of AGIC annotations and whether Application Gateway for
8282

8383
Migration from Application Gateway Ingress Controller to Application Gateway for Containers is designed to be a four step process:
8484

85-
1) [Step 1](#step-1-install-alb-controller): Install Application Gateway for Containers' ALB Controller
86-
2) [Step 2](#step-2-translate-ingress): Translate AGIC Ingress to Application Gateway for Containers Ingress
87-
3) [Step 3](#step-3-perform-end-to-end-validation): Perform end-to-end testing against Application Gateway for Containers
88-
4) [Step 4](#step-4-direct-traffic-to-application-gateway-for-containers): Direct traffic from AGIC to Application Gateway for Containers
85+
[Step 1](#step-1-install-alb-controller): Install Application Gateway for Containers' ALB Controller
86+
[Step 2](#step-2-translate-ingress): Translate AGIC Ingress to Application Gateway for Containers Ingress
87+
[Step 3](#step-3-perform-end-to-end-validation): Perform end-to-end testing against Application Gateway for Containers
88+
[Step 4](#step-4-direct-traffic-to-application-gateway-for-containers): Direct traffic from AGIC to Application Gateway for Containers
8989

9090
Steps 2 through 4 will be repeated for each service you plan to migrate.
9191

0 commit comments

Comments
 (0)